homepage

>>> 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 "<pyshell#8>", line 1, in <module>
 ast.literal_eval('{1,2}')
 File "C:\Python31\lib\ast.py", line 80, in literal_eval
 return _convert(node_or_string)
 File "C:\Python31\lib\ast.py", line 79, in _convert
 raise ValueError('malformed string')
ValueError: malformed string
>>> 
I haven't tested for 2.7 or 3.2 but this bug probably applies also there.

This is fixed in 3.2 (see r82804). As it is a new feature, it is not backported to 2.7 or earlier.

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.

2010年10月18日 Éric Araujo <report@bugs.python.org>:
>
> Éric Araujo <merwok@netwok.org> 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.
No change please.

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.'

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.

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)