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 paul.moore
Recipients eryksun, gaborjbernat, paul.moore, steve.dower, tim.golden, zach.ware
Date 2020-10-12.18:04:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1602525871.07.0.556536080947.issue42013@roundup.psfhosted.org>
In-reply-to
Content
I'm inclined to think that creating a venv from within another venv should be allowed. Tools like pipx can result in *other* tools being run from within a virtual environment, and I don't think it's good to disallow that usage - as an example, I have virtualenv, tox and nox installed via pipx, and all of them create virtual environments.

So I'm +1 on fixing this by calling realpath.

I don't think we need to do anything special for --system-site-packages. The docs say "Give the virtual environment access to the system site-packages dir". If people are trying to chain venvs using it, they are misreading that comment - and the best they could hope for is to request that it's made clearer.
History
Date User Action Args
2020-10-12 18:04:31paul.mooresetrecipients: + paul.moore, tim.golden, zach.ware, eryksun, steve.dower, gaborjbernat
2020-10-12 18:04:31paul.mooresetmessageid: <1602525871.07.0.556536080947.issue42013@roundup.psfhosted.org>
2020-10-12 18:04:31paul.moorelinkissue42013 messages
2020-10-12 18:04:31paul.moorecreate