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 djromberg
Recipients djromberg
Date 2021-01-27.14:42:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The copy operation is not safe to use during iteration. The following test case raises a "RuntimeError: dictionary changed size during iteration":

import weakref

class Class:

def TEST_weakValue():
  d = weakref.WeakValueDictionary()
  a = Class()
  b = Class()
  d["a"] = a
  d["b"] = b
  e = d.copy()
  for key in e:
    a = None
    c = e.copy()


This is related to where I commented as well, but I couldn't find a way to reopen this issue, which is why I open this one.

We experience a lot fewer crashes in weakref than before had been fixed, however, there are recursive situations in which copy() is invoked while iterating the WeakValueDictionary (e.g., in our case it is a signal/slot implementation where the slots are stored in a WeakValueDictionary). _commit_removals(), which is called at the beginning of the copy operation, might change the dictionary if there are items that are to be removed. If there is an ongoing iteration, the corresponding RuntimeError is raised.

I haven't thought that through entirely, but I wonder whether the copy (and also deepcopy) operation could just blindly copy everything without "committing removals". After the copy, both instances would do their _commit_removals on their own upon access.
Date User Action Args
2021-01-27 14:42:22djrombergsetrecipients: + djromberg
2021-01-27 14:42:22djrombergsetmessageid: <>
2021-01-27 14:42:22djromberglinkissue43041 messages
2021-01-27 14:42:22djrombergcreate