[issue31155] Encode set, frozenset, bytearray, and iterators as json arrays

2021-10-07 Thread sedrubal
Change by sedrubal : -- nosy: +sedrubal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.o

[issue31155] Encode set, frozenset, bytearray, and iterators as json arrays

2019-04-08 Thread Inada Naoki
Inada Naoki added the comment: I concur with Raymond. If you really need this feature, please discuss on python-dev ML. -- nosy: +inada.naoki resolution: -> rejected stage: -> resolved status: open -> closed ___ Python tracker

[issue31155] Encode set, frozenset, bytearray, and iterators as json arrays

2018-04-26 Thread Raymond Hettinger
Raymond Hettinger added the comment: There is some virtue to the current design. Having a user explicitly cast to a list will avoid unintentional conversions. -- nosy: +rhettinger ___ Python tracker ___

[issue31155] Encode set, frozenset, bytearray, and iterators as json arrays

2018-04-26 Thread Ori Avtalion
Ori Avtalion added the comment: If sets are to be supported, then so should dictionary views. Please also consider the range type. -- nosy: +salty-horse ___ Python tracker ___

[issue31155] Encode set, frozenset, bytearray, and iterators as json arrays

2017-08-09 Thread Raymond Hettinger
Changes by Raymond Hettinger : -- assignee: -> bob.ippolito nosy: +bob.ippolito ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue31155] Encode set, frozenset, bytearray, and iterators as json arrays

2017-08-09 Thread Javen O'Neal
New submission from Javen O'Neal: Currently json.dump, json.dumps, and json.JSONEncoder do not support writing iterator objects. Users can choose to pass the iterator to a tuple and write that as a json array, but this is wasteful if the iterator is large, requiring a large amount of memory to