Author tim.peters
Recipients docs@python, iabervon, tim.peters
Date 2020-06-30.02:41:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1593484890.58.0.368164908015.issue41133@roundup.psfhosted.org>
In-reply-to
Content
I don't see real value in the docs noting that Bad Things can happen if code lies about true refcounts. If a container points to an object, _of course_ the container should own that reference. Cheating on that isn't intended to be supported in any way, so there's no obligation to explain how or why things can go wrong otherwise. Worse, trying to explain such things would constrain implementations to have the same specific kinds of failure modes forever after. Neither would there would be real value in repeating "DON'T LIE ABOUT REFCOUNTS!" on every page, either ;-)

If someone just wants to know more about CPython's cyclic collector, that's fine, but that takes a great many more words than are suitable in the C API docs. Luckily, Pablo recently did that:

https://devguide.python.org/garbage_collector/
History
Date User Action Args
2020-06-30 02:41:30tim.peterssetrecipients: + tim.peters, docs@python, iabervon
2020-06-30 02:41:30tim.peterssetmessageid: <1593484890.58.0.368164908015.issue41133@roundup.psfhosted.org>
2020-06-30 02:41:30tim.peterslinkissue41133 messages
2020-06-30 02:41:30tim.peterscreate