Current State of Python Packaging
stefanoborini.com
Current State of Python Packaging
1–10 of 77 posts
Re: Current State of Python Packaging
#2I get mad at the Haskell tools I use every day, and then I remember that nobody else is really in better shape.
Re: Current State of Python Packaging
#3Never head of poetry before. Looks very nice. Thanks for sharing.
Re: Current State of Python Packaging
#4I get mad at the Haskell tools I use every day, and then I remember that nobody else is really in better shape.
Rust's Cargo is incredibly well thought-out and will make you despise everything else.
Re: Current State of Python Packaging
#5I get mad at the Haskell tools I use every day, and then I remember that nobody else is really in better shape.
Rust's Cargo is incredibly well thought-out and will make you despise everything else.
From the little development I have done in Rust, I have to agree.
On the other hand, I’ve been working with react-Native and typescript recently, and it’s a constant mess. Every invocation of yarn leaves at least a couple of warning messages about things that are out of my control. Installing packages is slow and at least every few days I have to wipe out node_modules and nuke any iOS build folders in order to get it working again. That said, RN is promising technology and hopefully my frustrations are due to more inexperience than the tools or language and ecosystem. I just wish all of the JavaScript stuff were faster. I’m on a gigabit connection and fast hardware but still it seems sometimes yarn has to download or unpack 6500 files or something
Re: Current State of Python Packaging
#6I get mad at the Haskell tools I use every day, and then I remember that nobody else is really in better shape.
Racket has by far the best I have ever used.
Here is everything you need to know about it in a 7 minute read.
Re: Current State of Python Packaging
#7Never head of poetry before. Looks very nice. Thanks for sharing.
Me either. Of course, now the last four Python packaging systems are obsolete. ("What about eggs? easy install? .egg-info directories? Forget them. They are legacy.")
The consistent problem with all these systems is that when (not if) an install fails, figuring out what to do is very difficult.
Re: Current State of Python Packaging
#8I get mad at the Haskell tools I use every day, and then I remember that nobody else is really in better shape.
Rust's Cargo is incredibly well thought-out and will make you despise everything else.
Nope. Absolutely not. Cargo makes the simple things easy but is less thought out than Rust itself.
Re: Current State of Python Packaging
#9I get mad at the Haskell tools I use every day, and then I remember that nobody else is really in better shape.
Racket has by far the best I have ever used. Here is everything you need to know about it in a 7 minute read. https://docs.racket-lang.org/pkg/getting-started.html
Yes I'm familiar with Racket.
Re: Current State of Python Packaging
#10Thought I would mention pip-tools as an option to manage requirements.txt.