bpo-39159: Declare errors that might be raised from literal_eval

[isidentical]

https://bugs.python.org/issue39159

[rhettinger]

Let's also take this opportunity to be more specific about what is meant by "numbers". Replace that with "ints, floats, complex numbers".

Also, please make the same update to the docstring for ast.literal_eval().

[rhettinger]

Just for my edification and for future reference, can you add a non-displayed in-line documentation comment showing an example of how each of these could happen.

[isidentical]

import ast

recursion_tuple = ast.Tuple(elts=[], ctx=ast.Load())
recursion_tuple.elts.append(recursion_tuple)
INPUTS = [
    ("invalid syntax", SyntaxError),
    ("test", ValueError),
    (ast.List(elts=None, ctx=ast.Load()), TypeError),
    (recursion_tuple, RecursionError),
]

for inp, exc_type in INPUTS:
    try:
        ast.literal_eval(inp)
    except exc_type:
        continue
    else:
        assert False

does something like this suits?

[isidentical]

@rhettinger or maybe we can put this in an actual test in test_ast and refer it? How does that sounds?

[taleinat]

Ping, @rhettinger?

[rhettinger]

Triggering a rebuild.