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 Stephen Moore
Recipients Stephen Moore, barry, ned.deily, r.david.murray, ronaldoussoren, vinay.sajip
Date 2017-10-02.23:15:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1506986140.73.0.213398074469.issue31660@psf.upfronthosting.co.za>
In-reply-to
Content
It appears the problem doesn't appear when using python3 -m venv.

Also it seems __PYVENV_LAUNCHER__ is set to the virtualenv's python except when it's a python3.6 virtualenv and we os.execv from python3.6, where it's set the system python.

Should I be making an issue with the virtualenv project?
History
Date User Action Args
2017-10-02 23:15:40Stephen Mooresetrecipients: + Stephen Moore, barry, vinay.sajip, ronaldoussoren, ned.deily, r.david.murray
2017-10-02 23:15:40Stephen Mooresetmessageid: <1506986140.73.0.213398074469.issue31660@psf.upfronthosting.co.za>
2017-10-02 23:15:40Stephen Moorelinkissue31660 messages
2017-10-02 23:15:40Stephen Moorecreate