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 r.david.murray
Recipients Filip Haglund, ahrvoje, ezio.melotti, r.david.murray
Date 2015-11-03.21:57:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1446587853.85.0.768274086917.issue24663@psf.upfronthosting.co.za>
In-reply-to
Content
Like I said, you should take your use case to python-ideas, for a safe_eval that would handle it.  literal_eval is not the place for handing 'set()', in my opinion.  (There is always a chance other other devs will disagree, but none have so far :).

FYI, reprs are often evalable to get back the original value, but the key word there is 'eval', not 'literal_eval'.
History
Date User Action Args
2015-11-03 21:57:33r.david.murraysetrecipients: + r.david.murray, ezio.melotti, Filip Haglund, ahrvoje
2015-11-03 21:57:33r.david.murraysetmessageid: <1446587853.85.0.768274086917.issue24663@psf.upfronthosting.co.za>
2015-11-03 21:57:33r.david.murraylinkissue24663 messages
2015-11-03 21:57:33r.david.murraycreate