I just tried this on a fully dist-upgraded sid machine: @chemistry[~:1005]% virtualenv -p python3.5 /tmp/p35 Running virtualenv with interpreter /usr/bin/python3.5 Using base prefix '/usr' New python executable in /tmp/p35/bin/python3.5 Also creating executable in /tmp/p35/bin/python Installing setuptools, pkg_resources, _markerlib, pip, wheel...done. @chemistry[~:1006]% source /tmp/p35/bin/activate (p35) @chemistry[~:1007]% pip install world Collecting world Using cached world-3.1.1-py2.py3-none-any.whl Requirement already satisfied (use --upgrade to upgrade): setuptools in /tmp/p35/lib/python3.5/site-packages (from world) Installing collected packages: world Successfully installed world-3.1.1 (p35) @chemistry[~:1008]% world it it originates from ITALY (p35) @chemistry[~:1009]% deactivate
Just a couple of days ago, Matthias uploaded a new version of Python 3.5 which includes the fix for python3-venv, although I don't *think* that shouldn be directly related to problems with pip inside virtualenv created venvs. http://metadata.ftp-master.debian.org/changelogs/main/p/python3.5/python3.5_3.5.1-8_changelog Still: @chemistry[~:1012]% python3.5 -m venv /tmp/v @chemistry[~:1013]% source /tmp/v/bin/activate (v) @chemistry[~:1014]% pip install world Collecting world Using cached world-3.1.1-py2.py3-none-any.whl Requirement already satisfied (use --upgrade to upgrade): setuptools in /tmp/v/lib/python3.5/site-packages (from world) Installing collected packages: world Successfully installed world-3.1.1 (v) @chemistry[~:1015]% world it it originates from ITALY (v) @chemistry[~:1016]% deactivate I also tried running tox with a py35 environment on a couple of my upstreams and they worked just fine. Can you make sure your system is fully updated and try again? If it's still crashing for you, then Something Else Is Going On. _______________________________________________ Python-modules-team mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
