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 vinay.sajip
Recipients Antony.Lee, vinay.sajip
Date 2017-11-22.07:22:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> I don't understand why things would be different when nesting?

Specifically because venv keeps "a pointer" to the Python environment it was created from. Usually that's a system Python. If a venv ("inner") is created from a virtualenv's interpreter, the pointer points back to that environment ("outer", in this case).

Also, virtualenv can re-invoke itself with a different interpreter easily - that's business as usual. However, the venv module is part of a specific Python stdlib and doesn't reinvoke itself with a different interpreter.

To find the exact mechanisms which lead to these behaviours, you would need to examine the code of virtualenv and the venv module and perhaps do some stepping through in a debugger!
Date User Action Args
2017-11-22 07:22:44vinay.sajipsetrecipients: + vinay.sajip, Antony.Lee
2017-11-22 07:22:44vinay.sajipsetmessageid: <>
2017-11-22 07:22:44vinay.sajiplinkissue30811 messages
2017-11-22 07:22:44vinay.sajipcreate