3 ms·
>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 (
by 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.