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 gregory.p.smith
Recipients Erik.Tollerud, amaury.forgeotdarc, eric.araujo, eric.snow, gregory.p.smith, meador.inge, psimons, python-dev, serhiy.storchaka, tomdzk
Date 2020-03-04.23:00:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1583362859.53.0.304421114261.issue13487@roundup.psfhosted.org>
In-reply-to
Content
Serhiy: Why is dict.copy() not thread safe?

if what you say of list(dict) being safe, iterating over that and looking up the keys would work.  But all of this is entirely non-obvious to the reader of the code.  all of these _look_ like they should be safe.

We should make dict.copy() safe and document the guarantee as such as that one could at least be explained when used for that purpose.
History
Date User Action Args
2020-03-04 23:00:59gregory.p.smithsetrecipients: + gregory.p.smith, amaury.forgeotdarc, eric.araujo, meador.inge, python-dev, eric.snow, Erik.Tollerud, serhiy.storchaka, psimons, tomdzk
2020-03-04 23:00:59gregory.p.smithsetmessageid: <1583362859.53.0.304421114261.issue13487@roundup.psfhosted.org>
2020-03-04 23:00:59gregory.p.smithlinkissue13487 messages
2020-03-04 23:00:59gregory.p.smithcreate