Author pablogsal
Recipients ericvw, pablogsal, pitrou, tzickel, vstinner
Date 2019-01-13.22:04:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I have been playing with possible solutions for a while and the weak-reference solution seems not robust enough as there are too potential race conditions between the destruction of the weakreferences (the pool) and the handling code.

I would advocate again for using a strong reference. The reasons are:

* The rest of the stdlib is using this solution to link iterator objects and similar to their parents (lists, dicts, sets...etc all have strong references back to their parents).

* This solution is backwards compatible with the current behaviour.

* We have the new ResourceWarnigns to make clear that this behaviour is not supported.
Date User Action Args
2019-01-13 22:04:01pablogsalsetrecipients: + pablogsal, pitrou, vstinner, ericvw, tzickel
2019-01-13 22:04:00pablogsalsetmessageid: <>
2019-01-13 22:04:00pablogsallinkissue35378 messages
2019-01-13 22:04:00pablogsalcreate