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 scoder
Recipients asvetlov, eli.bendersky, gphemsley, mdk, p-ganssle, r.david.murray, scoder, serhiy.storchaka, thatiparthy
Date 2019-04-21.06:23:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1555827814.59.0.466926558487.issue36685@roundup.psfhosted.org>
In-reply-to
Content
Instead of always copying the dict in create_new_element(), we should make sure that all code that calls that function (directly or indirectly) does so with a safely owned dict. If that means that we need to add dict copying in some other place, then that's what's needed to fix this bug.

The best fix is to make the copy close to the user input, where we know what we received and how we will continue to use it.
History
Date User Action Args
2019-04-21 06:23:34scodersetrecipients: + scoder, r.david.murray, eli.bendersky, asvetlov, serhiy.storchaka, thatiparthy, mdk, p-ganssle, gphemsley
2019-04-21 06:23:34scodersetmessageid: <1555827814.59.0.466926558487.issue36685@roundup.psfhosted.org>
2019-04-21 06:23:34scoderlinkissue36685 messages
2019-04-21 06:23:34scodercreate