bpo-39159: Declare error that might be raised from literal_eval (GH-19899)

This commit is contained in:
Batuhan Taskaya 2020-12-22 03:15:40 +03:00 committed by GitHub
parent b8fde8b541
commit fbc7723778
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 1 deletions

View File

@ -1576,7 +1576,7 @@ and classes for traversing abstract syntax trees:
Safely evaluate an expression node or a string containing a Python literal or Safely evaluate an expression node or a string containing a Python literal or
container display. The string or node provided may only consist of the container display. The string or node provided may only consist of the
following Python literal structures: strings, bytes, numbers, tuples, lists, following Python literal structures: strings, bytes, numbers, tuples, lists,
dicts, sets, booleans, and ``None``. dicts, sets, booleans, ``None`` and ``Ellipsis``.
This can be used for safely evaluating strings containing Python values from This can be used for safely evaluating strings containing Python values from
untrusted sources without the need to parse the values oneself. It is not untrusted sources without the need to parse the values oneself. It is not
@ -1588,6 +1588,10 @@ and classes for traversing abstract syntax trees:
sufficiently large/complex string due to stack depth limitations sufficiently large/complex string due to stack depth limitations
in Python's AST compiler. in Python's AST compiler.
It can raise :exc:`ValueError`, :exc:`TypeError`, :exc:`SyntaxError`,
:exc:`MemoryError` and :exc:`RecursionError` depending on the malformed
input.
.. versionchanged:: 3.2 .. versionchanged:: 3.2
Now allows bytes and set literals. Now allows bytes and set literals.