[issue24663] ast.literal_eval does not handle empty set literals
New submission from Filip Haglund:
ast.literal_eval handles sets, if they contain at least one value, but does not
handle empty ones, which are represented as `set()` since `{}` is already used
by dicts.
--
components: Library (Lib)
messages: 246906
nosy: Filip Haglund
priority: normal
severity: normal
status: open
title: ast.literal_eval does not handle empty set literals
versions: Python 3.4
___
Python tracker
<http://bugs.python.org/issue24663>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24663] ast.literal_eval does not handle empty set literals
Filip Haglund added the comment: Okey, then this is not a bug. I can just handle this special case myself. Thanks! -- status: pending -> closed ___ Python tracker <http://bugs.python.org/issue24663> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue26077] Make slicing of immutable structures return a view instead of a copy
New submission from Filip Haglund: Slicing tuples returns a copy, which is O(n) time. This could be O(1) since tuples are immutable, by just pointing to the same data. This probably applies to other immutable structures as well, such as strings. -- components: Interpreter Core messages: 257937 nosy: Filip Haglund priority: normal severity: normal status: open title: Make slicing of immutable structures return a view instead of a copy type: performance versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6 ___ Python tracker <http://bugs.python.org/issue26077> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
