3 ms·
> Unfortunately, Conda poses some challenges if/when you need to take a project that lives in a Conda environment and transfer it to a more typical Python packa
by disgruntledphd2 5y ago
> Unfortunately, Conda poses some challenges if/when you need to take a project that lives in a Conda environment and transfer it to a more typical Python package, mostly because Conda environments can control things like the C compiler, while Python package managers cannot.
To be honest, having been in this situation it generally makes more sense to implement the pip dependencies inside the conda venv (by running pip), as conda can handle the C-level dependencies and pip is mostly perfect (modulo back when it didn't actually manage dependencies) for pure python stuff.
Also, it sounds like you know a lot about python packaging, please by the love of all that's holy, write this stuff down somewhere other than HN. There really isn't a lot of good docs around this.
- nerdponx 5y agoThat's pretty much how I've done the Conda transition too. Switch to using Pip inside the Conda env to suss out what the non-Python deps are. Also a lot of packages are distributed on PyPI as binary packages now, so as long as you aren't using Musl in production you should just be able to use those instead. > Also, it sounds like you know a lot about python packaging, please by the love of all that's holy, write this stuff down somewhere other than HN. There really isn't a lot of good docs around this. Believe me, I want to! I am pretty bad at managing my "project/writing wishlist".