➜

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 dstufft
Recipients alex, barry, bkabrda, doko, dstufft, janssen, lemburg, ncoghlan, pitrou, r.david.murray, rkuska, vstinner
Date 2015-04-05.19:48:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1428263324.51.0.759551760573.issue23857@psf.upfronthosting.co.za>
In-reply-to
Content 
> No, I want to be able to easily disable the newly added
> checks in 2.7.9+ to get systems such as these behave the
> same as with 2.7.8, since without this option, people
> using these system are going to be forced to stick with
> buggy 2.7.8 systems.

Why is the monkeypatch in sitecustomize.py unacceptable? I understand why it's
unacceptable to Nick and rkuska, they are a vendor and they don't want to write
sitecustomize.py when the machine operator may want to use that file, however
you're the machine operator in this case.
History
Date User Action Args
2015-04-05 19:48:44dstufftsetrecipients: + dstufft, lemburg, barry, doko, ncoghlan, janssen, pitrou, vstinner, alex, r.david.murray, bkabrda, rkuska
2015-04-05 19:48:44dstufftsetmessageid: <1428263324.51.0.759551760573.issue23857@psf.upfronthosting.co.za>
2015-04-05 19:48:44dstufftlinkissue23857 messages
2015-04-05 19:48:44dstufftcreate