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 paul.moore, steve.dower, tim.golden, vinay.sajip, wolma, zach.ware
Date 2015-02-21.23:41:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
> As an alternative, virtualenv could be changed to create a pyvenv.cfg file with the interpreter version like pyvenv does. Seems pretty simple and unproblematic to me and it might actually be useful to know the interpreter version without running it in other places besides the launcher. What do the pypa devs think about this?

As one of the pypa devs, I'm in favour of this. I'll probably
implement it in due course, time permitting. But of course, a PR from
someone else would be a help :-)
Date User Action Args
2015-02-21 23:41:24paul.mooresetrecipients: + paul.moore, vinay.sajip, tim.golden, zach.ware, steve.dower, wolma
2015-02-21 23:41:24paul.moorelinkissue23465 messages
2015-02-21 23:41:24paul.moorecreate