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 potiuk
Recipients JelleZijlstra, malthe, potiuk, rhettinger
Date 2022-03-05.09:28:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1646472491.41.0.725935894023.issue46925@roundup.psfhosted.org>
In-reply-to
Content
How about if we make PR instead to the documentation about this behaviour? 

I think this behaviour is a little surprising (you need to know the internals of how WeakKeyDict keys are constructed and checked) and while I understand you do not want breaking change, maybe this should be explained to the users and example given how to apply the workaround?

Just following the "least surprise" principle.
History
Date User Action Args
2022-03-05 09:28:11potiuksetrecipients: + potiuk, rhettinger, malthe, JelleZijlstra
2022-03-05 09:28:11potiuksetmessageid: <1646472491.41.0.725935894023.issue46925@roundup.psfhosted.org>
2022-03-05 09:28:11potiuklinkissue46925 messages
2022-03-05 09:28:11potiukcreate