[issue10091] ast.literal_eval does not handled new set literals

Piotr Dobrogost added the comment: 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 Stackove

[issue10091] ast.literal_eval does not handled new set literals

nestor added the comment: FYI although it breaks symmetry with eval, I am fine with this going in for 3.2. It just surprised me and I wanted to make sure it was documented here for future reference. -- ___ Python tracker

[issue10091] ast.literal_eval does not handled new set literals

Raymond Hettinger added the comment: ast.literal_eval's docs: 'The string or node provided may only consist of the following Python literal structures: strings, numbers, tuples, lists, dicts, booleans, and None.' -- resolution: out of date -> invalid

[issue10091] ast.literal_eval does not handled new set literals

Benjamin Peterson added the comment: 2010/10/18 Éric Araujo : > > Éric Araujo added the comment: > > 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.  Benjamin, can you > make a statement as release manager?

[issue10091] ast.literal_eval does not handled new set literals

Éric Araujo added the comment: 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. Benjamin, can you make a statement as release manager? Thanks. -- nosy: +eric.araujo _

[issue10091] ast.literal_eval does not handled new set literals

Georg Brandl added the comment: This is fixed in 3.2 (see r82804). As it is a new feature, it is not backported to 2.7 or earlier. -- resolution: -> out of date status: open -> closed ___ Python tracker ___

[issue10091] ast.literal_eval does not handled new set literals

Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue10091] ast.literal_eval does not handled new set literals

New submission from nestor : >>> import ast >>> eval('{1:11,2:22}') {1: 11, 2: 22} >>> ast.literal_eval('{1:11,2:22}') {1: 11, 2: 22} >>> eval('{1,2}') {1, 2} >>> ast.literal_eval('{1,2}') Traceback (most recent call last): File "", line 1, in ast.literal_eval('{1,2}') File "C:\Python31