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 nanjekyejoannah
Recipients guijarro, nanjekyejoannah, nascheme, pablogsal
Date 2021-10-22.12:37:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1634906260.53.0.338384858584.issue45555@roundup.psfhosted.org>
In-reply-to
Content
I can reproduce the described scenario. I will nosy Pablo and Neil for another eye.

I suggest that if it's not a bug, then maybe the docs should be updated to explain this behavior.

The only part that talks about exceptions in the documentation for weakref.ref() reads as:

"""
Exceptions raised by the callback will be noted on the standard error output, but cannot be propagated; they are handled in exactly the same way as exceptions raised from an object’s __del__() method.
"""
History
Date User Action Args
2021-10-22 12:37:40nanjekyejoannahsetrecipients: + nanjekyejoannah, nascheme, pablogsal, guijarro
2021-10-22 12:37:40nanjekyejoannahsetmessageid: <1634906260.53.0.338384858584.issue45555@roundup.psfhosted.org>
2021-10-22 12:37:40nanjekyejoannahlinkissue45555 messages
2021-10-22 12:37:40nanjekyejoannahcreate