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 danpascu
Recipients asvetlov, danpascu, yselivanov
Date 2020-11-28.11:25:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1606562714.14.0.0923437902543.issue41562@roundup.psfhosted.org>
In-reply-to
Content
While it may not be affected at a functional level (at least not in a way I can see right now), it is confusing when reading that code.

Isn't clarity and avoiding confusion a desired trait for core python code?

What about all these recommendations from the Zen of Python?

Beautiful is better than ugly.
Simple is better than complex.
Flat is better than nested.
Readability counts.
If the implementation is hard to explain, it's a bad idea.
History
Date User Action Args
2020-11-28 11:25:14danpascusetrecipients: + danpascu, asvetlov, yselivanov
2020-11-28 11:25:14danpascusetmessageid: <1606562714.14.0.0923437902543.issue41562@roundup.psfhosted.org>
2020-11-28 11:25:14danpasculinkissue41562 messages
2020-11-28 11:25:14danpascucreate