[issue32151] -mvenv vs minor python version updates

2017-12-01 Thread Ronald Oussoren
Change by Ronald Oussoren : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___

[issue32151] -mvenv vs minor python version updates

2017-12-01 Thread Ric Anderson
Ric Anderson added the comment: well then, I guess y'all can close this ticket -- ___ Python tracker ___

[issue32151] -mvenv vs minor python version updates

2017-12-01 Thread Tzu-ping Chung
Tzu-ping Chung added the comment: Hmm, I’m quite sure I have experience that a virtual environment breaks after a micro version upgrade on macOS, getting an “image not found” or something similar. I’m not using the official released Python, but via Homebrew, so maybe this

[issue32151] -mvenv vs minor python version updates

2017-12-01 Thread Ronald Oussoren
Ronald Oussoren added the comment: The virtualenv (both using venv and using the third party library virtualenv) still relies on most of the python installation outside of the virtualenv, in particular the stdlib extensions. Those are not guartanteed to be binary

[issue32151] -mvenv vs minor python version updates

2017-11-30 Thread Tzu-ping Chung
Tzu-ping Chung added the comment: Not sure if it’s the same thing, but I want to plug in that this can happen when you do a micro upgrade (e.g. 3.5.1 → 3.5.2) as well. This is because micro updates sometimes bump versions of dependencies (e.g. OpenSSL, Tk), and that

[issue32151] -mvenv vs minor python version updates

2017-11-30 Thread Ric Anderson
Ric Anderson added the comment: Okay, are virtual env's expected to not be compatible as well? E.g., I built a venv under 3.5; venv copied in the 3.5 python executable, but not the needed library; should not -mvenv also copy libpython3.5 into the virutal setup or at

[issue32151] -mvenv vs minor python version updates

2017-11-29 Thread Ronald Oussoren
Ronald Oussoren added the comment: This is the expected behavior, the upgrade from 3.5 to 3.6 is a feature update that is (in general) not expected to be binary compatible with the previous release. -- nosy: +ronaldoussoren

[issue32151] -mvenv vs minor python version updates

2017-11-27 Thread Ric Anderson
New submission from Ric Anderson : When a site updates python3 from 3.5 to 3.6 (based on https://docs.python.org/3/faq/general.html#how-does-the-python-version-numbering-scheme-work, this is would be a minor version update),pre-upgrade venv setups created with "python3