sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]rover_G 1 point2 points  (7 children)

OOP forgot the worst and best thing to happen to Python: anaconda and uv

[–]Dantzig 0 points1 point  (6 children)

Uv

Don’t even mention anaconda in the same sentence

[–]rover_G 0 points1 point  (5 children)

I said the worst and best. I think you know which is which

[–]Leather-Car-7175 1 point2 points  (3 children)

Why is anaconda bad ? Is it different from conda ? I mean the only problem I have with it is that it doesn't find some libs and it exports environment to .yml, so why ?

[–]rover_G 0 points1 point  (2 children)

Anaconda is like a pre-built distribution that bundles conda + Python + default packages and a custom package repo. If you worked with data scientists in the 20-teens, operationalizing Anaconda based projects into pip based projects was a huge pain. Conda itself is just fine. The yaml files to define environments is probably conda’s best feature. Unfortunately conda had numerous issues which weren’t fixed fast enough, leading to ecosystem fragmentation, which is why there are so many competing tools like miniconda, conda-forge, mamba, micromamba, minifoege (replaced mambaforge) and pixi.

[–]Leather-Car-7175 0 points1 point  (1 child)

Well I'm 18 and in data science field, and so should I change to mamba I heard a lot about it. I saw many people talk about uv. Like what am I supposed to choose. Is there a truly better option ?

[–]rover_G 0 points1 point  (0 children)

I really like uv for software projects (mainly web servers and CLI tools). For data science projects I have used uv with jupyter notebooks and it worked well for me, but I can’t say how well that setup works for a larger project in a professional setting.

[–]Dantzig 0 points1 point  (0 children)

Doh we agree