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 nascheme
Recipients berker.peksag, cryvate, eric.araujo, nascheme, ncoghlan, ned.deily, pitrou, serhiy.storchaka, tarek, vstinner
Date 2017-12-02.22:48:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1512254895.08.0.213398074469.issue19610@psf.upfronthosting.co.za>
In-reply-to
Content
> Thank you, but I don't need a lecture from you. Feel free to propose our solution in the form of pull request instead of acting like a project manager and telling people what to do.

I'm sorry you are offended.  My pull request would consist of the patch being reverted.  It is not ready to go in.  If a change breaks a significant amount of previously working Python code, it needs very careful consideration and should be introduced in a way to minimize breakage and allow people time to fix their code.

Repeatably pointing to the documentation and saying that existing code is broken because it doesn't respect documented requirements is not okay.
History
Date User Action Args
2017-12-02 22:48:15naschemesetrecipients: + nascheme, ncoghlan, pitrou, vstinner, tarek, ned.deily, eric.araujo, berker.peksag, serhiy.storchaka, cryvate
2017-12-02 22:48:15naschemesetmessageid: <1512254895.08.0.213398074469.issue19610@psf.upfronthosting.co.za>
2017-12-02 22:48:15naschemelinkissue19610 messages
2017-12-02 22:48:14naschemecreate