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 steve.dower
Recipients christian.heimes, nedbat, pablogsal, steve.dower
Date 2021-12-11.00:10:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I'm going to need a decent amount of time to learn all of these components, because I never use this OS, Tox, nor virtualenv :) I'll try and get to it, but don't hold your breath. Luckily, Modules/ is much easier to follow and modify than the old systems.

If there's a pyvenv.cfg involved, base_executable should be calculated based on the "home" key in it. Previously, I don't think we calculated it at all on Linux - it was just sys.executable before changes anything.

On Windows, it was always intended to be "the executable that new venvs should be created with" so that venvs created from venvs would be based off the same install, rather than trying to chain. I have no idea what the correct path for that is in this context, so could do with some help.
Date User Action Args
2021-12-11 00:10:22steve.dowersetrecipients: + steve.dower, christian.heimes, nedbat, pablogsal
2021-12-11 00:10:22steve.dowersetmessageid: <>
2021-12-11 00:10:22steve.dowerlinkissue46028 messages
2021-12-11 00:10:22steve.dowercreate