5 ms·
It's own environments mechanisms is even better: each environment can have it's own separate python version! The "miniconda" installer variant is something I e
by nnq 9y ago
It's own environments mechanisms is even better: each environment can have it's own separate python version!
The "miniconda" installer variant is something I even use in production when on the same server I need to run microservices one written fro Python 2.4, another for Pythn 2.7+, another for Python 3.3, another for Python 3.6+ etc.
Really, anyone doing Python should embrace conda envs - they are awesome and allow skipping the entire "Python 2 or 3" useless discussion and replacing it with "just use whatever python you want", just specify it clearly... The whole "2 vs 3" incident would never even have existed if people people would've had something like Node's NVM or Ruby's RVM, and "conda envs" it's basically this, only that it combines support for its own special package formats with this.
- captainmuon 9y agoYou can do that with virtualenvs, too. `mkvirtualenv -p python3.6` for example. When you activate that virtualenv, it uses that interpreter version.
- nnq 9y agoCan you also install separate python versions this way? like have it automagically download a precompiled python3.6 for you even if there may not be a distro package for it. I don't really like having to depend on the system's python binaries and their packages, but I don't want to compile my own either. But I do know most people would violently disagree with me on this :) (I just happen to be both incredibly lazy and a control freak at the same time :P...)
- afarrell 9y agoyes, you just need to find a channel that has that version published, trust the person maintaining that channel, and do something like `conda install --channel amfarrell nodejs=6.6.0`
- nnq 9y agoI was asking the question about non-anaconda python, aka "plain python with virtualenv" that I think GP was referring to...
- afarrell 9y agoYou can also install your own separate nodejs version in each environment. Or your own separate ruby version.
- danso 9y ago> The whole "2 vs 3" incident would never even have existed if people people would've had something like Node's NVM or Ruby's RVM, and "conda envs" it's basically this, only that it combines support for its own special package formats with this. What is this "2 vs 3" incident and how would a better version manager solved the problem of Py2 packages not migrating to 3?