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 tim.peters
Recipients Dennis Sweeney, rhettinger, serhiy.storchaka, tim.peters
Date 2022-02-04.05:42:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Raised the priority back to normal.

I agree with Dennis's observation that PyDict_Next is safe, provided it's used as intended: it returns borrowed references, but to things that absolutely are legitimate at the time. In the presence of mutations, *what* it returns isn't defined at all, but I don't see a way for it to blow up (unless its caller screws up by believing it owns the references). It doesn't assume anything about the structure of the dict across calls.
Date User Action Args
2022-02-04 05:42:31tim.peterssetrecipients: + tim.peters, rhettinger, serhiy.storchaka, Dennis Sweeney
2022-02-04 05:42:31tim.peterssetmessageid: <>
2022-02-04 05:42:31tim.peterslinkissue46615 messages
2022-02-04 05:42:30tim.peterscreate