@chaospatterns to [email protected]English • 5 months agoPython has too many package managersdublog.netmessage-square40arrow-up180arrow-down16
arrow-up174arrow-down1external-linkPython has too many package managersdublog.net@chaospatterns to [email protected]English • 5 months agomessage-square40
minus-square@[email protected]linkfedilinkEnglish10•5 months agoI’ve tried several and all of them left be disappointed eventually.
minus-square@[email protected]linkfedilink3•5 months agoNot OP. I ended up using hatch to make packages because it’s simple and does everything without feeling like a jumbled mess of tools like Poetry. It feels unix-like and didn’t prevent from doing my job.
minus-square@[email protected]linkfedilink1•edit-25 months agoHatch is great. It’s easy to get started but I wouldn’t call it simple. Flit is simple, because it’s limited. Hatch is complex enough to allow you to override everything, which makes it not simple, but also not complicated.
minus-square@demizeronelink2•3 months agoI landed on hatch. The way it handles venvs and python versioning is awesome, and can also use UV. I haven’t used UV yet tho.
I’ve tried several and all of them left be disappointed eventually.
What did you end up using for your workflow?
Not OP. I ended up using hatch to make packages because it’s simple and does everything without feeling like a jumbled mess of tools like Poetry. It feels unix-like and didn’t prevent from doing my job.
Hatch is great. It’s easy to get started but I wouldn’t call it simple. Flit is simple, because it’s limited.
Hatch is complex enough to allow you to override everything, which makes it not simple, but also not complicated.
I landed on hatch. The way it handles venvs and python versioning is awesome, and can also use UV. I haven’t used UV yet tho.