➜

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 Jens Lindgren
Recipients Jens Lindgren, Steve Barnes, eryksun, paul.moore, ricpol, steve.dower, tim.golden, vinay.sajip, wdhwg001, zach.ware
Date 2017-06-07.13:49:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1496843366.12.0.339316850972.issue28686@psf.upfronthosting.co.za>
In-reply-to
Content 
I just got hit by this bug and would like to add my thoughts on this.
If you are in an activated venv, no matter if you launch with command python or python3, it will launch the version in venv (version 3.6.1 in this case).
I expect the py-launcher and shebang to work the same way. In fact it works as expected on Linux and '#! /usr/bin/env pyton3' are in fact using the venv version.
This is a pretty major bug that needs to be fixed asap in my opinion.
History
Date User Action Args
2017-06-07 13:49:26Jens Lindgrensetrecipients: + Jens Lindgren, paul.moore, vinay.sajip, tim.golden, zach.ware, eryksun, steve.dower, wdhwg001, ricpol, Steve Barnes
2017-06-07 13:49:26Jens Lindgrensetmessageid: <1496843366.12.0.339316850972.issue28686@psf.upfronthosting.co.za>
2017-06-07 13:49:26Jens Lindgrenlinkissue28686 messages
2017-06-07 13:49:26Jens Lindgrencreate