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-04.17:39:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1646415577.09.0.545588788762.issue46896@roundup.psfhosted.org>
In-reply-to
Content
> Why so coarse?

> Getting a notification for every change of a global in module, is likely to make use the use of global variables extremely expensive.

Perhaps a compromise is possible here: one global group/chain of callbacks registered for all dictionaries in an interpreter seems reasonable (to keep overhead low), but we could reduce the number of times it’s actually called by, say, tagging specific values of specific dictionaries to be watched.

For example, we could just tag the low bit of any pointer in a dictionary’s values that we want to be notified of changes to. Something like that seems like it could really keep the cost of watching down without sacrificing power.
History
Date User Action Args
2022-03-04 17:39:37brandtbuchersetrecipients: + brandtbucher, barry, gregory.p.smith, carljm, dino.viehland, Mark.Shannon, itamaro
2022-03-04 17:39:37brandtbuchersetmessageid: <1646415577.09.0.545588788762.issue46896@roundup.psfhosted.org>
2022-03-04 17:39:37brandtbucherlinkissue46896 messages
2022-03-04 17:39:37brandtbuchercreate