➜

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 pablogsal
Recipients BTaskaya, pablogsal, rhettinger, serhiy.storchaka
Date 2020-01-03.19:40:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1578080429.1.0.34389659698.issue39158@roundup.psfhosted.org>
In-reply-to
Content 
> The function literal_eval is not safe anymore as the constructor can be intercepted:

Well, actually it can also be done with any other builtin via the same trick, so this is no different but is only slightly more obvious that it can be done.

I still find a bit weird that the documentation says "literal or container display" but 'set' is neither.
History
Date User Action Args
2020-01-03 19:40:29pablogsalsetrecipients: + pablogsal, rhettinger, serhiy.storchaka, BTaskaya
2020-01-03 19:40:29pablogsalsetmessageid: <1578080429.1.0.34389659698.issue39158@roundup.psfhosted.org>
2020-01-03 19:40:29pablogsallinkissue39158 messages
2020-01-03 19:40:29pablogsalcreate