Luis Norambuena@programming.dev to Python@programming.devEnglish · 1 day agouv IS the Future of Python Packaging 🐍📦www.youtube.comexternal-linkmessage-square33fedilinkarrow-up133arrow-down17file-text
arrow-up126arrow-down1external-linkuv IS the Future of Python Packaging 🐍📦www.youtube.comLuis Norambuena@programming.dev to Python@programming.devEnglish · 1 day agomessage-square33fedilinkfile-text
minus-squaresugar_in_your_tea@sh.itjust.workslinkfedilinkarrow-up2·22 hours agoYeah, it certainly looks nice, but my problems are: everything runs in a docker container locally, so I don’t think the caching is going to be a huge win we have a half-dozen teams and a dozen repositories or so, across three time zones, so big changes require a fair amount of effort we just got through porting to poetry to split into dependency groups, and going back to not having that is a tough sell So for me, it needs to at least have feature parity w/ poetry to seriously consider.
minus-squaremonogram@feddit.nllinkfedilinkEnglisharrow-up1·13 hours agoYou should be using dockers cache mounts https://docs.docker.com/build/cache/optimize/#use-cache-mounts
minus-squareEager Eagle@lemmy.worldlinkfedilinkEnglisharrow-up1·edit-219 hours agouv is still faster with a cold cache and uv does have dep groups about the second problem, there’s an issue open on writing a migration guide, but migrating manually is not too difficult.
Yeah, it certainly looks nice, but my problems are:
So for me, it needs to at least have feature parity w/ poetry to seriously consider.
You should be using dockers cache mounts
https://docs.docker.com/build/cache/optimize/#use-cache-mounts
uv is still faster with a cold cache
and uv does have dep groups
about the second problem, there’s an issue open on writing a migration guide, but migrating manually is not too difficult.