3 ms·

I have a tendency to install one of python 2.x and one of python 3.x and then use the --python flag to set the particular python I want my project to run agains

I have a tendency to install one of python 2.x and one of python 3.x and then use the --python flag to set the particular python I want my project to run against. At that point it should work invisibly in the virtualenv. Unlike ruby, point releases don't often make sweeping breaking changes so it is often enough to say 'this is python 3 code' or 'this is python 2 > 2.5' code, so the granularity of something like pyenv is mostly unnecessary, imo.

dham 11y ago
That's the way I worked at my last job with Python. I filed for brain fuckery bankruptcy after trying to get pyenv and pyenv virtualevnwrapper set up. You can't say this is Python 3 code or Python 2 code. That's completely false. If someone used latest features from Python 3.5 that wouldn't work on 3.4. Also, I haven't had any issues upgrading point releases in Ruby(since 2.0). Point releases do not make sweeping changes by any means. You maybe talking about the weird 1.8 to 1.9.3 thing.