Marc-Andre Lemburg added the comment: On 05.04.2015 21:48, Donald Stufft wrote: > > Donald Stufft added the comment: > >> 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.
I don't consider monkey patching a proper way to configure a Python installation. I could simply patch the Python installation directly, but this is just me. I'm talking about sys admins out there who don't know enough about Python to be able to patch Python or write a sitecutomize.py which uses monkey patching to fix the issue. I also cannot recommend to our customers to monkey patch Python just to get it running again. This is not what folks expect from a production quality system :-) ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue23857> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
