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 carljm
Recipients barry, benjamin.peterson, carljm, georg.brandl, jaraco, loewis
Date 2012-03-29.21:10:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1333055426.25.0.85502391807.issue14444@psf.upfronthosting.co.za>
In-reply-to
Content
There's no question that this is a case of virtualenv allowing users to do something that's not supported.

Nonetheless, virtualenv is very widely used, and in practice it does not break "more often". This, however, will break for lots of users, and those users will (wrongly) perceive the breakage to be caused by a Python security bugfix, not by virtualenv.

I think the purity argument is completely correct, but this certainly seems like a situation where practicality might nonetheless beat purity.
History
Date User Action Args
2012-03-29 21:10:26carljmsetrecipients: + carljm, loewis, barry, georg.brandl, jaraco, benjamin.peterson
2012-03-29 21:10:26carljmsetmessageid: <1333055426.25.0.85502391807.issue14444@psf.upfronthosting.co.za>
2012-03-29 21:10:25carljmlinkissue14444 messages
2012-03-29 21:10:25carljmcreate