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 vstinner
Recipients Ned Williamson, giampaolo.rodola, gvanrossum, methane, ned.deily, vstinner, yselivanov
Date 2016-12-14.09:21:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
_asyncio_Future_remove_done_callback() is still wrong with  Issue28963.patch: what if an evil __eq__() methods inserts or remove directly items of the future callbacks list?

By design, it's not safe to iterate on a list if the body of the list calls arbitrary Python code.

(I don't know how exactly, but everything in Python is possible, see the gc module to retrieve private fields of a C objecct.)
Date User Action Args
2016-12-14 09:21:08vstinnersetrecipients: + vstinner, gvanrossum, giampaolo.rodola, ned.deily, methane, yselivanov, Ned Williamson
2016-12-14 09:21:08vstinnersetmessageid: <>
2016-12-14 09:21:08vstinnerlinkissue28963 messages
2016-12-14 09:21:08vstinnercreate