zlacker

[return to "Uv 0.3 – Unified Python packaging"]
1. ilaksh+oR1[view] [source] 2024-08-21 12:31:55
>>mantap+(OP)
Ok so stupid question.. even though the majority of package documentation seems to mention pip, it's very dated, right? And I have only been trying to focus a bit more on python the last couple of years, so actually I just found out about poetry like last month. But poetry is also very uncool now right?

Most people not on the bleeding edge use conda, not poetry? But people who are hip use rye and uv? Up until today and now they only use uv if possible?

I'm actually building a system around user-installed plugins. Where there is a UI to search for and install plugins on the fly.

Also one other thing just to double check, it is now very uncool or considered bad practice to use dynamic or flexible types in Python?

◧◩
2. thraxi+7S1[view] [source] 2024-08-21 12:38:11
>>ilaksh+oR1
Conda is mainly used by ML, AI, and data science people and to a certain extent feels like its own separate ecosystem. In other areas, like web dev, conda use is pretty rare.
◧◩◪
3. ilaksh+wT1[view] [source] 2024-08-21 12:50:31
>>thraxi+7S1
Ok so for web dev, are most projects using poetry, the, or something else?
◧◩◪◨
4. wswope+OW2[view] [source] 2024-08-21 20:15:23
>>ilaksh+wT1
Most projects do just fine with pip + venv, and that’s what they stick to.

The exception is if they have specific dependencies outside the CPython ecosystem - in which case they’ll probably be using conda. Examples of such dependencies include nodejs/cuda/cublas/specific versions of gcc. Webdev generally doesn’t have as many of these dependencies compared to the data world, which is why conda is less popular there.

Speaking in sweeping generalities here: you probably don’t need poetry, uv, or kin - at all. But there’s nothing wrong with choosing to use them if you prefer to do so either.

[go to top]