chaospatterns@lemmy.world to Python@programming.devEnglish · 4 months agoPython has too many package managersdublog.netexternal-linkmessage-square38fedilinkarrow-up179arrow-down16
arrow-up173arrow-down1external-linkPython has too many package managersdublog.netchaospatterns@lemmy.world to Python@programming.devEnglish · 4 months agomessage-square38fedilink
minus-squarehenfredemars@infosec.publinkfedilinkEnglisharrow-up12arrow-down2·4 months agoI’ve tried several and all of them left be disappointed eventually.
minus-squareericjmorey@programming.devlinkfedilinkarrow-up2·4 months agoWhat did you end up using for your workflow?
minus-squarebest_username_ever@sh.itjust.workslinkfedilinkarrow-up3·4 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-squareflying_sheep@lemmy.mllinkfedilinkarrow-up1·edit-24 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.
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.