4 ms·
I will never understand all these posts about Python packaging. It's not the best, but at least it isn't Gradle or Maven or Bundler or Podfile or NPM/Webpack/ts
by odie5533 2y ago
I will never understand all these posts about Python packaging. It's not the best, but at least it isn't Gradle or Maven or Bundler or Podfile or NPM/Webpack/tsconfig/eslint/babel nonsense. When I install a JavaScript library, I have to edit like 5 different files to get it to start working. And god forbid I upgrade, then I have to read the migration docs every single time because every upgrade choice they make is unique.
Latest headache: eslint completely changed the config file so now you have to convert your old file, oh and your plugins don't work so you need to use the plugin compatibility shims that also don't work.
I think some of the hate for Python packaging is that it's everyone's first foray into the packaging world since it's everyone's first programming language. I think if Python were a more difficult language, people wouldn't complain about the packaging at all.
- zahlman 2y ago>It's not the best, but at least it isn't I think it's good to be able to criticize the things you like best. And thinking that someone else might be having a worse experience, doesn't improve my own. Many common complaints about Python packaging are things I don't find valid. I chose to get that stuff out of the way, before getting into the stuff that does concern me (including things that I don't commonly hear others mention).