This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients GreenKey, emilyemorehouse, ncoghlan, r.david.murray
Date 2017-06-14.02:17:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Emily's answer sort of covered the "It's not as simple as it might seem" aspect, whereby the bit that's genuinely tricky is to provide access to the system pip(/setuptools/wheel) without providing accessing to the system site packages in general.

If the latter is actually considered desirable, then the most suitable venv configuration is likely to be:

    python3 -m venv --system-site-packages --without-pip

as that will give you a fresh venv to install your own additions into, but use the system pip package by default, rather than automatically bootstrapping a venv specific instance of it.

We don't currently discuss that kind of hybrid configuration in the docs, so it may be appropriate to reopen this as a docs issue, and add a new "How do I use system level Python packages from a virtual environment?" question to
Date User Action Args
2017-06-14 02:17:10ncoghlansetrecipients: + ncoghlan, r.david.murray, GreenKey, emilyemorehouse
2017-06-14 02:17:10ncoghlansetmessageid: <>
2017-06-14 02:17:10ncoghlanlinkissue30628 messages
2017-06-14 02:17:09ncoghlancreate