3 ms·
Looks like Conda is still the best package/env manager for ML engineers.
by p1esk 2y ago
Looks like Conda is still the best package/env manager for ML engineers.
- dmd 2y agoUnfortunately I'm still waiting for "Solving environment". It's been 8 years. Please send help. I'm so hungry. (Yes, I know about mamba.)
- LarsDu88 2y agoI lol'd at this. At my last job, we lost days if not weeks to "solving environment" due to poetry and many folks not understanding that ceiling pinning is BAD when you use a tool like poetry to manage your deps.
- hrpnk 2y agoPoetry user here. What is so special about Conda that makes it particularly good for ML use cases?
- p1esk 2y agoNo idea, I just summarized TFA.
- gillesjacobs 2y agoML engineer, I am up to 3 irreversibly broken environments after simply adding a package. Conda is inexcusably slow and but even mamba can save it. Every conda project I have ever was later switched to poetry. Here's a fun challenge: try to determine channel priority in your conda env, go ahead try. Conda is the single worst packaging tool I have ever used.
- p1esk 2y agoOK, would you say poetry is the best for ML engineers?
- gillesjacobs 2y agoPoetry worked best in several Python-first companies and clients I have worked for. It's not perfect but the best bet for complex and collaboration-heavy projects.
- klxamb 2y agoFirst I need to create enough space for my comment: /root/miniconda3/build/_placehold_placehold_placehold_placehold_placehold_pplacehold_placehold_placehold_placehold_placehold_p ... Seriously, conda can be pretty annoying for packagers. I don't like the Jinja configuration stuff, I don't like the chaotic build output (see above), sometimes libraries are leaking in from the system, for some undocumented issues it takes ages to search for an answer. One everything is set up, things tend to work, apart from the slow solver. I also do not like the way that conda embeds itself in the Windows installation. It is a bit overhyped, like all things in the "scientific" ecosystem.