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 rhettinger
Recipients Dennis Sweeney, rhettinger, serhiy.storchaka
Date 2022-02-03.16:42:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1643906534.15.0.576271807029.issue46615@roundup.psfhosted.org>
In-reply-to
Content
Presumably _PyDict_Next is also suspect.  Even the advertised "safe" calls to PyDict_SetItem() for existing keys would be a trigger.  Calling clear() in either __eq__ or __hash__ would suffice.

If the next loops are the culprint, the new challenge is figuring out how to fix it without wrecking code clarity and performance (and having to deprecate PyDict_Next() which is part of the stable ABI).
History
Date User Action Args
2022-02-03 16:42:14rhettingersetrecipients: + rhettinger, serhiy.storchaka, Dennis Sweeney
2022-02-03 16:42:14rhettingersetmessageid: <1643906534.15.0.576271807029.issue46615@roundup.psfhosted.org>
2022-02-03 16:42:14rhettingerlinkissue46615 messages
2022-02-03 16:42:14rhettingercreate