3 ms·
I was looking this morning at migrating our software from poetry to uv at my company, due to poetry's slowness. And so far i've been reading a lot of doc and no
by fvdessen 2y ago
I was looking this morning at migrating our software from poetry to uv at my company, due to poetry's slowness. And so far i've been reading a lot of doc and not getting a lot things done. I did the previous migration to poetry as well which was vastly simpler. So far it seems that poetry tried to make a simple package manager that works like any other, while uv is keeping quite a bit of the python package insanity around.
- burntsushi 2y agoAre there any specifics you can share about what you found difficult to do in uv?
- bvrmn 2y agoAt least uv doesn't lead to an absolute clusterfuck of poetry conflicting with virtualenv. Or broken package.toml format with minor poetry changes. Or amazingly dumb "sources" which doesn't work for transitive dependencies and leads to even longer resolve times in case of multiple indexes.
- seabrookmx 2y agoHow does it conflict with virtualenv? Last I checked it's default behavior was to automagically create a virtualenv for you if you run it from system python (a bit weird but ok) or if you were in an virtualenv, it would use it. For our projects we use pyenv-virtualenv (so we can have specific python versions per project) and then poetry "just works" (though can be slow, hence rye, uv and friends).
- orbisvicis 2y agoTo which insanities are you referring?
- bschwindHN 2y agoProbably the entirety of the current python package management ecosystem. From the outside, it all looks insane but I suppose most users are Stockholm-syndrome-d into thinking everything is fine.
- yoyohello13 2y agoWe just recently migrated to uv from pip-tools and it was pretty seamless. uv pretty much just plugs into the standard python tooling workflow.
- pas 2y agoyou probably want Rye (as uv is too low-level for now), no?
- kzrdude 2y agouv does rye's job as of uv 0.3. More or less, anyway.
- deleted 2y ago[deleted]