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 yurzo
Recipients steven.daprano, yurzo
Date 2020-10-01.16:37:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Thanks for your prompt answer Steven.

I was inspired to file this bug after reading through a multiplicity of bugs introduced by folks confused by the library's behavior. So there's good precedent.

While granted, the documentation is explicit and the inheritance chain substantiates it. There's nothing more explicit than the function/type names and saying brings, as you say, arbitrary time to the conversation. Which I claim, subjectively, that it should not.

Gratuitous breakage, is debatable. It would not be the first or last. It could be a chance to remove a lot of code that works around potentially incorrect mental models.

But since both points are to some extent subjective. I'm OK to have left this on the record and move on.

What do you say about the unnecessarily redefined properties?

Lines Lib/ to
Date User Action Args
2020-10-01 16:37:28yurzosetrecipients: + yurzo, steven.daprano
2020-10-01 16:37:28yurzosetmessageid: <>
2020-10-01 16:37:28yurzolinkissue41904 messages
2020-10-01 16:37:28yurzocreate