4 ms·
Your position seems to be that Python packaging is a mess for non-specific reasons but also that nobody is allowed to write tools to improve usability. Think ab
by acdha 6y ago
Your position seems to be that Python packaging is a mess for non-specific reasons but also that nobody is allowed to write tools to improve usability. Think about pip – that wasn't the first tool to do that job but it (gasp) automated several things which didn't have great solutions. Virtualenv has the same story. This will be no different.
> I can find and install updates just fine in other package managers for other languages, without messing my setup.
Just like Python, in other words? (remember, this thread is not about installing package updates)
> I can also move my whole environment to any path I like (with just copying).
The problem we're talking about here is what happens when you get a new build of the language itself. This is also true of most other dynamic languages unless you manage to avoid using any sort of native code linked against the language runtime. A compiled language which produces a static binary won't need that, of course, but that doesn't avoid the need to periodically recompile to stay current with dependencies and language changes. In all of these cases, automation makes the process fast and easy.
- coldtea 6y ago>Your position seems to be that Python packaging is a mess for non-specific reasons No, for very specific reasons. Historical cruft, too many competing tools (from pip to conda, and from venv to poetry, not to mention setuptools), conceptual garbage like wheels, pths, etc., non-movable virtual environments, and so on. >The problem we're talking about here is what happens when you get a new build of the language itself. This is also true of most other dynamic languages unless you manage to avoid using any sort of native code linked against the language runtime. And yet node handles this much more elegantly (with C++/gyp modules). And minor releases should absolutely no need this.