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 BTaskaya, docs@python, pablogsal, rhettinger, serhiy.storchaka
Date 2020-01-06.19:24:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> The function literal_eval is not safe anymore as the 
> constructor can be intercepted

"Safe" means safe from user input to literal_eval().

If a person can already write arbitrary code that redefines a builtin, then they can already do anything they want.
Date User Action Args
2020-01-06 19:24:07rhettingersetrecipients: + rhettinger, docs@python, serhiy.storchaka, pablogsal, BTaskaya
2020-01-06 19:24:07rhettingersetmessageid: <>
2020-01-06 19:24:06rhettingerlinkissue39158 messages
2020-01-06 19:24:06rhettingercreate