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 georg.brandl
Recipients Behdad.Esfahbod, docs@python, georg.brandl
Date 2014-09-30.17:40:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1412098831.08.0.82619239068.issue22525@psf.upfronthosting.co.za>
In-reply-to
Content
The function is still called literal_eval(), not safe_eval().

I'm not saying a safe eval() isn't useful.  But an implementation that is only partly safe is not going to help anyone.
History
Date User Action Args
2014-09-30 17:40:31georg.brandlsetrecipients: + georg.brandl, docs@python, Behdad.Esfahbod
2014-09-30 17:40:31georg.brandlsetmessageid: <1412098831.08.0.82619239068.issue22525@psf.upfronthosting.co.za>
2014-09-30 17:40:31georg.brandllinkissue22525 messages
2014-09-30 17:40:30georg.brandlcreate