3 ms·

With libraries that alter your path at runtime. I've encountered comments on issues that implied that this wasn't a complete hack. I have had the impression tha

With libraries that alter your path at runtime. I've encountered comments on issues that implied that this wasn't a complete hack. I have had the impression that this is all just overhead in getting an environment up and running, and not taken for granted that you should be able to achieve repeatable isolation relatively simply. So I think even if one of those packaging tools worked really well, a library somewhere could undo your best efforts at isolation. I also don't hate python itself, but I wish the one way of doing things ethos applied to managing dependencies and python versions.

fock 4y ago
I don't understand what the problem is: 1) you install ONE version of python, more can't coexist in your environment usually 2) then you install your packages in a venv (because python provides tools to configure this) Only part 2 is a problem of the Python ecosystem, part 1 is a problem of any environment to run binary programs. It applies to C-compilers, node, ..., perl... Naturally, as most people involved with Python seemed to agree with that view, there was a lot of room for "improvement". And people got their improvement aplenty. Other people just realized that this is a general problem and nowadays instead of keeping around their /opt they now use something like spack. Which allows you to install a range of python-versions just fine. As well as C-Compilers. As well as perl-versions.