On Thu, Dec 14, 2017 at 01:33:18PM +0100, Krzysztof Słychań wrote: > after upgrading system-wide Python installation (in my case from 3.5.3 to > 3.5.4), > virtualenvs may break due to the outdated interpreter > (somevirtualenv/bin/python3) inside the venv, trying to work with a newer > stdlib. This is in no way specific to virtualenvwrapper which is just a wrapper.
> The problem is that mkvirtualenv copies rather than symlinks the python > interpreter binary, but symlinks the modules from standard library (e.g. > /usr/lib/python3.5). This is done by virtualenv, not mkvirtualenv, and it was always that way, and it's quite well known that the breakages happen and how to fix them (by running virtualenv again). It is done because otherwise Python would not find some files using relative paths. See also https://github.com/pypa/virtualenv/pull/1171 and note "only for Python 3.3 and higher". -- WBR, wRAR
signature.asc
Description: PGP signature
