4 ms·
How is this a treat not clear it's not straightforward and not obvious as to how to switch back-and-forth between 2.7 and 3.5 why are there two dangling version
by noloblo 9y ago
How is this a treat not clear it's not straightforward and not obvious as to how to switch back-and-forth between 2.7 and 3.5 why are there two dangling versions
- detaro 9y agofor projects you only use with one Python version, you have a virtualenv per project, with the right version, and enable the virtualenv when you work on that project. (or you only do that for the python version you use less, but virtualenvs have more benefits than just managing python versions). If you need to test something with two versions, you have one env per python version and enable whichever one you need.