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 corona10, pablogsal, serhiy.storchaka, shihai1991, tim.peters, vstinner
Date 2020-04-07.17:52:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1586281921.36.0.0264609208243.issue40217@roundup.psfhosted.org>
In-reply-to
Content
> We cannot change all user code, so we should change the interpreter code so that it will work correctly with existing user code.

If we made a change that make all user code suddenly incorrect, that change should be reverted. The GC has clear rules about what tp_traverse should and should not do, and we should not violate those rules and make special cases in the gc just because we forced some classes to be incorrect. This will make much more difficult to reason about GC bugs, the tp_traverse implementation of classes and much difficult to maintain the GC itself.
History
Date User Action Args
2020-04-07 17:52:01pablogsalsetrecipients: + pablogsal, tim.peters, vstinner, serhiy.storchaka, corona10, shihai1991
2020-04-07 17:52:01pablogsalsetmessageid: <1586281921.36.0.0264609208243.issue40217@roundup.psfhosted.org>
2020-04-07 17:52:01pablogsallinkissue40217 messages
2020-04-07 17:52:01pablogsalcreate