[issue39159] Ideas for making ast.literal_eval() usable
Batuhan Taskaya
report at bugs.python.org
Fri Feb 14 16:13:46 EST 2020
Batuhan Taskaya <batuhanosmantaskaya at gmail.com> added the comment:
> 1) We should document possible exceptions that need to be caught. So far, I've found TypeError, MemoryError, SyntaxError, ValueError.
Also, an addition to these errors is RecursionError
>>> t = ast.Tuple(elts=[], ctx=ast.Load())
>>> t.elts.append(t)
>>> ast.literal_eval(t)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/local/lib/python3.9/ast.py", line 101, in literal_eval
return _convert(node_or_string)
File "/usr/local/lib/python3.9/ast.py", line 81, in _convert
return tuple(map(_convert, node.elts))
File "/usr/local/lib/python3.9/ast.py", line 81, in _convert
return tuple(map(_convert, node.elts))
File "/usr/local/lib/python3.9/ast.py", line 81, in _convert
return tuple(map(_convert, node.elts))
[Previous line repeated 496 more times]
RecursionError: maximum recursion depth exceeded
----------
_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue39159>
_______________________________________
More information about the Python-bugs-list
mailing list