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 Oren Milman, geeknik, lemburg, pitrou, serhiy.storchaka, tim.peters, twouters, vstinner
Date 2017-10-06.20:46:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <[email protected]>
In-reply-to
Content
> This is different case than mutating a dict while iterate it. In this case the failure is caused by GC, and it is always hard to handle such issues. In case of a dict you can just copy it before iterating. But what to do with RuntimeError from slicing a list if copying a list is vulnerable to the same issue?

This issue was found by fuzzing with weird destructor. I don't think that anyone will hit the bug with "normal" code in the wild. Otherwise, we would have get a bug report before this one.
History
Date User Action Args
2017-10-06 20:46:00vstinnersetrecipients: + vstinner, lemburg, tim.peters, twouters, pitrou, serhiy.storchaka, Oren Milman, geeknik
2017-10-06 20:46:00vstinnersetmessageid: <[email protected]>
2017-10-06 20:46:00vstinnerlinkissue31165 messages
2017-10-06 20:46:00vstinnercreate