This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients BTaskaya, docs@python, pablogsal, rhettinger, serhiy.storchaka
Date 2020-01-04.13:41:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The documentation for ast.literal_eval():

   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
   following Python literal structures: strings, bytes, numbers, tuples, lists,
   dicts, sets, booleans, and ``None``.

If we are going to add support of a function call set(), we should change the documentation.

And if add support of non-literals, where should we stop? Should we support also frozenset() and bytearray()? inf and nan? infj and nanj? complex()? Ellipsis? __debug__?
Date User Action Args
2020-01-04 13:41:21serhiy.storchakasetrecipients: + serhiy.storchaka, rhettinger, docs@python, pablogsal, BTaskaya
2020-01-04 13:41:21serhiy.storchakasetmessageid: <>
2020-01-04 13:41:21serhiy.storchakalinkissue39158 messages
2020-01-04 13:41:21serhiy.storchakacreate