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 Antony.Lee
Recipients Antony.Lee, vinay.sajip
Date 2017-11-22.07:03:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1511334219.37.0.213398074469.issue30811@psf.upfronthosting.co.za>
In-reply-to
Content
> venv, on the other hand, doesn't, but keeps a reference to its original Python environment. That is, I think, the reason for the difference in behaviour.

But for example, using the system Python to create a venv (no nesting), packages installed system-wide (e.g. using a linux package manager) are not visible in the venv.  Or, as you note, nesting a venv into another works fine.  I don't understand why things would be different when nesting?

In any case thanks for the workaround.
History
Date User Action Args
2017-11-22 07:03:39Antony.Leesetrecipients: + Antony.Lee, vinay.sajip
2017-11-22 07:03:39Antony.Leesetmessageid: <1511334219.37.0.213398074469.issue30811@psf.upfronthosting.co.za>
2017-11-22 07:03:39Antony.Leelinkissue30811 messages
2017-11-22 07:03:39Antony.Leecreate