➜

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 piotr.dobrogost
Recipients aronacher, benjamin.peterson, eric.araujo, ezio.melotti, georg.brandl, gpolo, mark.dickinson, nestor, piotr.dobrogost, rhettinger, terry.reedy
Date 2012-07-21.19:52:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1342900359.35.0.678764299624.issue10091@psf.upfronthosting.co.za>
In-reply-to
Content 
I totally agree with Eric's statement that "Set literals, a new feature indeed, have been backported to 2.7 and 3.1.  The lack of support in ast.literal_eval is arguably a bug."
I came here from "set literal syntax support in Python 2.7" question at Stackoverflow (http://stackoverflow.com/q/6078262/95735)
History
Date User Action Args
2012-07-21 19:52:39piotr.dobrogostsetrecipients: + piotr.dobrogost, georg.brandl, rhettinger, terry.reedy, mark.dickinson, benjamin.peterson, gpolo, aronacher, ezio.melotti, eric.araujo, nestor
2012-07-21 19:52:39piotr.dobrogostsetmessageid: <1342900359.35.0.678764299624.issue10091@psf.upfronthosting.co.za>
2012-07-21 19:52:38piotr.dobrogostlinkissue10091 messages
2012-07-21 19:52:38piotr.dobrogostcreate