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 pablogsal
Recipients eric.snow, leezu, pablogsal, pitrou, rhettinger, tim.peters, vstinner
Date 2020-03-02.19:10:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> I agree the tp_traverse docs should point out that weakref lists are special this way, but I think the problem is unique to them - can't think of another case where a container points to an object it doesn't own a reference to.

Agreed, I was thinking a small warning or something because this is not the first time I see similar errors or users confused about what they should and should not track (with this I mention that we should say that "only objects that are *owned* should be tracked, and then the weakref warning or something similar). I will prepare a PR soon.
Date User Action Args
2020-03-02 19:10:36pablogsalsetrecipients: + pablogsal, tim.peters, rhettinger, pitrou, vstinner, eric.snow, leezu
2020-03-02 19:10:36pablogsalsetmessageid: <>
2020-03-02 19:10:36pablogsallinkissue39778 messages
2020-03-02 19:10:36pablogsalcreate