I'm unclear if issues relating to the python3 venv module should be reported here. If not, please direct me somewhere else so I can spam them instead. :)
This seems to be related to this (though whatever fix is mentioned there isn't available): https://groups.google.com/forum/#!searchin/python-virtualenv/site-packages$20does$20not$20install$20pip|sort:relevance/python-virtualenv/oLm21KXY5TI/sFnS_JGDT1kJ The issue can be replicated as follows. Download and compile a fresh python 3.6 installation and make sure it's on your path. Next if you run the following command $ python3 -m venv venv tt will add symlinks to pip and pip3 in your virtual environment. If you run this command $ python3 -m venv --system-site-packages venv It will _not_ symlink pip and pip3. As a result, in the second case you cannot install packages using pip3 when your environment is activated (it attempts to install them in the base distribution). You can always still use pip to install in your virtual environment this way though: `python -m pip install blah`. It's kind of annoying and can be very confusing. Also the fact that both debian and Ubuntu ship the `python3-pip` and `python3-venv` packages separately means that if you don't have `python3-pip` installed, then the problem disappears (i.e. the pip/pip3 files are symlinked even when --system-site-packages is passed). However if you install `python3-pip` the problem comes back. Is this the intended behavior? -- You received this message because you are subscribed to the Google Groups "virtualenv" group. To unsubscribe from this group and stop receiving emails from it, send an email to python-virtualenv+unsubscr...@googlegroups.com. To post to this group, send email to python-virtualenv@googlegroups.com. Visit this group at https://groups.google.com/group/python-virtualenv. For more options, visit https://groups.google.com/d/optout.
