STINNER Victor added the comment: _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.) ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28963> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
