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 a-feld, deekay, pablogsal, tim.peters
Date 2020-04-20.17:03:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1587402215.24.0.607256715994.issue40312@roundup.psfhosted.org>
In-reply-to
Content
> Pablo, as above, I'm inclined to leave things alone unless we can "prove" no current code could possibly be relying (even by accident) on that gc currently runs callbacks before finalizers.  Which may be the case!  I don't know ;-)

I very much agree with this. Also, (I think you already mentioned this) over-specifying the order of things in the gc may be a great way to shoot ourselves in the foot if we need to fix bugs or some odd behaviour during finalization/destruction (think for instance the latest bug regarding tp_clear and weakref callbacks).

I think we could at least improve somehow the docs, to say at least that the order is not specified so people that look at them do not rely on it.
History
Date User Action Args
2020-04-20 17:03:35pablogsalsetrecipients: + pablogsal, tim.peters, a-feld, deekay
2020-04-20 17:03:35pablogsalsetmessageid: <1587402215.24.0.607256715994.issue40312@roundup.psfhosted.org>
2020-04-20 17:03:35pablogsallinkissue40312 messages
2020-04-20 17:03:35pablogsalcreate