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 dalke
Recipients alex, benjamin.peterson, dalke, eryksun, holdenweb, methane, ncoghlan, pitrou, serhiy.storchaka, vstinner
Date 2017-05-23.16:03:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1495555388.8.0.476724935562.issue21074@psf.upfronthosting.co.za>
In-reply-to
Content
Again, I do not propose any changes to the existing optimizer. I do not need anything changed for my code to work.

My goal is to counter-balance comments which suggest that perfectly normal code is somehow folly and arcane. These caused me some bewilderment and self-doubt as I tried to establish that my test suite was not, in fact, poorly written. Others with the same issue should not face the same confusion. 

I especially do not want to see the years of experience with the current optimizer used to justify repeating the same decisions in some future AST-based optimizer. http://bugs.python.org/issue2506#msg64764 gives an example of how the lack of complaints over several years is used to argue against changing compiler behavior.

Terms like "folly" and "arcane" also suggest an outright rejection of considering to support in the future what seems like totally reasonable code. 

I realize now that there is a more immediately actionable item. I have just added #30440 as a request to document these effects. I have removed my name from its nosy list in hopes of reducing Raymond Hettinger's concerns about comfort and safety, and thus perhaps increase the likelihood that this will be documented.

"I apologize if you were offended", which I will take as being sincere, happens to also be one of the most common examples of an insincere apology. Bowing out when there is a reference to the CoC gives undue power to others, and hinders the ability to apply its spirit to all but the most egregious situations.

Even if I accept the idea that "sane" and "insane" have technical meanings, that does not exempt their use from questions about being considerate and respective. Django and others replaced their use of the technical terms "master" and "slave", following a trend which is at least 13 years old; see http://edition.cnn.com/2003/TECH/ptech/11/26/master.term.reut/ . Note that I am not proposing to avoid using the terms "sane" and "insane", only asserting that there is no clean exception for words which also have a technical sense or meaning, even when used for that technical sense.
History
Date User Action Args
2017-05-23 16:03:08dalkesetrecipients: + dalke, holdenweb, ncoghlan, pitrou, vstinner, benjamin.peterson, alex, methane, serhiy.storchaka, eryksun
2017-05-23 16:03:08dalkesetmessageid: <1495555388.8.0.476724935562.issue21074@psf.upfronthosting.co.za>
2017-05-23 16:03:08dalkelinkissue21074 messages
2017-05-23 16:03:08dalkecreate