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 brandtbucher
Recipients Mark.Shannon, barry, brandtbucher, carljm, dino.viehland, gregory.p.smith, itamaro
Date 2022-03-03.20:15:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1646338500.37.0.546832709309.issue46896@roundup.psfhosted.org>
In-reply-to
Content
> CPython will track only one global callback; it is a well-behaved client’s responsibility to check if a callback is already set when setting a new one, and daisy-chain to the previous callback if so.

Hm, this is a bit scary. Could we (or others) end up with unguarded stale caches if some buggy extension forgets to chain the calls correctly?

Core CPython seems most at risk of this, since we would most likely be registered first.
History
Date User Action Args
2022-03-03 20:15:00brandtbuchersetrecipients: + brandtbucher, barry, gregory.p.smith, carljm, dino.viehland, Mark.Shannon, itamaro
2022-03-03 20:15:00brandtbuchersetmessageid: <1646338500.37.0.546832709309.issue46896@roundup.psfhosted.org>
2022-03-03 20:15:00brandtbucherlinkissue46896 messages
2022-03-03 20:15:00brandtbuchercreate