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 eryksun
Recipients eryksun, paul.moore, schlamar, steve.dower, tim.golden, zach.ware
Date 2019-02-02.23:37:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> You can't actually nest virtual environments, at least with venv

Yes, they can't be nested in terms of inheriting site-packages. But the "home" value in this case references the creating environment, which hasn't changed from previous versions. It's the same in Linux. In my first message I suggested having the launcher resolve pyvenv.cfg files until it finds the real python.exe to execute (the first one with no pyvenv.cfg file), thus bypassing the intervening launchers.

> What is in your pyvenv.cfg files here?

They're as expected:

    C:\>type C:\Temp\test\env37_1\pyvenv.cfg
    home = C:\Program Files\Python37
    include-system-site-packages = false
    version = 3.7.2

    C:\>type C:\Temp\test\env37_2\pyvenv.cfg
    home = C:\Temp\Test\env37_1\scripts
    include-system-site-packages = false
    version = 3.7.2
Date User Action Args
2019-02-02 23:37:58eryksunsetrecipients: + eryksun, paul.moore, tim.golden, schlamar, zach.ware, steve.dower
2019-02-02 23:37:56eryksunsetmessageid: <>
2019-02-02 23:37:56eryksunlinkissue35872 messages
2019-02-02 23:37:55eryksuncreate