Re:Ask HN: How do you handle/maintain local Python environme...
by w8rbt on Monday September 23, 2019 @09:18PM
(#21055517)
This is my biggest issue with Python. I absolutely love the language, but Python 3 ought to be Python 3 no matter where/how you got it. If you are using 3.5 and I'm using 3.7 we ought to be able to share code and things just work. Unfortunately, that is not the case.
[ Parent
| on HN ]
Re:Ask HN: How do you handle/maintain local Python environme...
by jnwatson on Monday September 23, 2019 @10:16PM
(#21055847)
Why would that not work?
Re:Ask HN: How do you handle/maintain local Python environme...
by torte on Monday September 23, 2019 @11:42PM
(#21056288)
There are some breaking features from added in 3.7 which were not in the language in 3.7. Meaning code written for the newer Python 3 version might not work with the older Python 3 version. Most of those additions are relatively easy to fix though.
Code from an older Python 3 version should always work in the newer Python 3 version though (at least for 3.5 -> 3.7).
Re:Ask HN: How do you handle/maintain local Python environme...
by mdtusz on Tuesday September 24, 2019 @08:52AM
(#21059532)
You'd think, but it's not always the case. I've recently encountered an issue with eventlet that is only present in 3.7, for example.
Re:Ask HN: How do you handle/maintain local Python environme...
by snorkasaurus on Tuesday September 24, 2019 @10:05AM
(#21060281)
I agree. Try pyenv. It lets you install a particular version for use in a shell account, then `python -m venv venv`. I like pip-tools for requirements management, but some reasonable people disagree.