chaospatterns@lemmy.world to Python@programming.devEnglish · 1 year agoPython has too many package managersdublog.netexternal-linkmessage-square38linkfedilinkarrow-up179arrow-down16
arrow-up173arrow-down1external-linkPython has too many package managersdublog.netchaospatterns@lemmy.world to Python@programming.devEnglish · 1 year agomessage-square38linkfedilink
minus-squareericjmorey@programming.devlinkfedilinkarrow-up2·1 year agoWhat did you end up using for your workflow?
minus-squarebest_username_ever@sh.itjust.workslinkfedilinkarrow-up3·1 year 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-squareflying_sheep@lemmy.mllinkfedilinkarrow-up1·edit-21 year 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.
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.