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:29:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1446586179.1.0.894747002554.issue24663@psf.upfronthosting.co.za>
In-reply-to
Content
You haven't presented an actual use case, it would be interesting to see one.

Regardless of that, however, ast.literal_eval is an exposure of the literal value parsing part of the AST.  set() is not part of that, because it is not a literal, it is a function call.

There has been some discussion of adding a "safe_eval" function to the stdlib (see issue 22525), and that would be the appropriate place to introduce evaluation of set().

python-ideas would be the appropriate place to discuss safe_eval.
History
Date User Action Args
2015-11-03 21:29:39r.david.murraysetrecipients: + r.david.murray, ezio.melotti, Filip Haglund, ahrvoje
2015-11-03 21:29:39r.david.murraysetmessageid: <1446586179.1.0.894747002554.issue24663@psf.upfronthosting.co.za>
2015-11-03 21:29:39r.david.murraylinkissue24663 messages
2015-11-03 21:29:38r.david.murraycreate