Message 398719 - Python tracker

➜

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	rhettinger
Recipients	carljm, graingert, ncoghlan, pydanny, rhettinger, serhiy.storchaka, tim.peters, ztane
Date	2021-08-01.18:06:38
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1627841198.07.0.0748006010085.issue43468@roundup.psfhosted.org>
In-reply-to

Content
> It is hard to get rid of the execution lock once > it was introduced, but I think we should do it. It's likely some apps are relying on the locking feature. So if we can fix it, we should do prefer that over more disruptive changes. Addenda to my code sketch: It should use "(id(instance), instance)" rather than just "instance" as the key.

> It is hard to get rid of the execution lock once 
> it was introduced, but I think we should do it.

It's likely some apps are relying on the locking feature.
So if we can fix it, we should do prefer that over more
disruptive changes.

Addenda to my code sketch:  It should use "(id(instance), instance)" rather than just "instance" as the key.

History
Date	User	Action	Args
2021-08-01 18:06:38	rhettinger	set	recipients: + rhettinger, tim.peters, ncoghlan, carljm, pydanny, serhiy.storchaka, ztane, graingert
2021-08-01 18:06:38	rhettinger	set	messageid: <1627841198.07.0.0748006010085.issue43468@roundup.psfhosted.org>
2021-08-01 18:06:38	rhettinger	link	issue43468 messages
2021-08-01 18:06:38	rhettinger	create