[issue25896] array.array accepting byte-order codes in format strings
New submission from Zoinkity .: I'd like to propose allowing the use of byte-order characters in the typecode string used by the array.array class. This removes any ambiguity on the order of the data, especially when that data is not known and loaded from an outside source. You wouldn't need to presume little or big endian machine byteorder or test the system to determine this. Also, it removes the necessity of byteswapping data that isn't in the correct order. -- components: Extension Modules messages: 256614 nosy: Zoinkity.. priority: normal severity: normal status: open title: array.array accepting byte-order codes in format strings type: enhancement versions: Python 3.6 ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue25896> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19548] 'codecs' module docs improvements
Zoinkity . added the comment: One glaring omission is any information about multibyte codecs--the class, its methods, and how to even define one. Also, the primary use for codecs.register would be to append a single codec to the lookup registry. Simple usage of the method only provides lookup for the provided codecs and will not include regularly-accessible ones such as utf-8. It would be enormously helpful to provide an example of proper, safe usage. -- nosy: +Zoinkity.. ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19548 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
