[issue32174] nonASCII punctuation characters can not display in python363.chm.
New submission from zaazbb : In chm(python363.chm) documents, some unicode chars (non ascii chars) can not display. for example: asyncio — Asynchronous I/O, event loop, coroutines and tasks displayed as asyncio � Asynchronous I/O, event loop, coroutines and tasks and Asynchronous programming is more complex than classical “sequential” programming display as Asynchronous programming is more complex than classical 搒equential� programming windows 10, simplified chinese language. python3.6.3, python363.chm. -- components: Windows files: 1512013191(1).jpg messages: 307277 nosy: paul.moore, steve.dower, tim.golden, zaazbb, zach.ware priority: normal severity: normal status: open title: nonASCII punctuation characters can not display in python363.chm. type: behavior versions: Python 3.6 Added file: https://bugs.python.org/file47304/1512013191(1).jpg ___ Python tracker <https://bugs.python.org/issue32174> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30943] printf-style Bytes Formatting sometimes do not worked.
New submission from zaazbb: # works. >>> b'\x00\x08%(amount)b'% {b'amount':b'1'} b'\x00\x081' # not work. >>> b'\x11\x00\x08%(amount)b'% {b'amount':b'1'} b'\x11\x00\x08%(amount)b' # not work. >>> amount=bytearray(b'0010') >>> posnum=bytearray(b'423') >>> date_ =b'170717' >>> time_=b'160006' >>> b'\x02\x03\x13\x9f\x00\x00\x04NULL\x9f\x01\x00\x01\x02\x9f\x03\x00\x0c\xd6\xd0\xb9\xfa\xd2\xf8\xc1\xaa\xb2\xe2\xca\xd4\x9f\x04\x00\x0f307310083980007\x9f\x05\x00\x0814025520\x9f\x14\x00\x0200\x9f\x19\x00\x08\xbd\xbb\xd2\xd7\xb3\xc9\xb9\xa6\x9f\x07\x00\x0803072900\x9f\x08\x00\n0014243000\x9f\t\x00\x08\xbd\xf0\xbf\xa8\xd6\xd0\xd0\xc4\x9f\n\x00\x0800092900\x9f\r\x00\x06000145\x9f\x0e\x00\x0681\x9f\x10\x00\x0c162246168268\x9f\x11\x00\x08%(date)s\x9f\x12\x00\x06%(time)s\x9f\x02\x00\x0c%(amount)s\x9f\x1b\x00\x04\x9f\x0b\x00\x13622452*2994\x9f\x0c\x00\x01S\x9f\x0f\x00\x00\x9f\x13\x00.FK:\xbb\xb7\xd3\xce\xd1\xc7\xcc\xab\xb3\xa9\xcf\xed\xd2\xf8\xc1\xaa\xd3\xc5\xbb\xdd\nZX:promo.unionpay.com\n\x9f\x1f\x00\x03%(posnum)s\x9f\x1a\x00\x00\x9f\xa1\x00\x01\x01\x9f\xa0\x00\x01\x01\x03\x00'% >>> {b'amount': amount,b'date': date_,b'time': time_,b'posnum': posnum} b'\x02\x03\x13\x9f\x00\x00\x04NULL\x9f\x01\x00\x01\x02\x9f\x03\x00\x0c\xd6\xd0\xb9\xfa\xd2\xf8\xc1\xaa\xb2\xe2\xca\xd4\x9f\x04\x00\x0f307310083980007\x9f\x05\x00\x0814025520\x9f\x14\x00\x0200\x9f\x19\x00\x08\xbd\xbb\xd2\xd7\xb3\xc9\xb9\xa6\x9f\x07\x00\x0803072900\x9f\x08\x00\n0014243000\x9f\t\x00\x08\xbd\xf0\xbf\xa8\xd6\xd0\xd0\xc4\x9f\n\x00\x0800092900\x9f\r\x00\x06000145\x9f\x0e\x00\x0681\x9f\x10\x00\x0c162246168268\x9f\x11\x00\x08%(date)s\x9f\x12\x00\x06%(time)s\x9f\x02\x00\x0c%(amount)s\x9f\x1b\x00\x04\x9f\x0b\x00\x13622452*2994\x9f\x0c\x00\x01S\x9f\x0f\x00\x00\x9f\x13\x00.FK:\xbb\xb7\xd3\xce\xd1\xc7\xcc\xab\xb3\xa9\xcf\xed\xd2\xf8\xc1\xaa\xd3\xc5\xbb\xdd\nZX:promo.unionpay.com\n\x9f\x1f\x00\x03%(posnum)s\x9f\x1a\x00\x00\x9f\xa1\x00\x01\x01\x9f\xa0\x00\x01\x01\x03\x00' Environment: Python 3.6.1 Windows 10 64bit. -- components: Library (Lib) messages: 298465 nosy: zaazbb priority: normal severity: normal status: open title: printf-style Bytes Formatting sometimes do not worked. type: behavior versions: Python 3.6 ___ Python tracker <http://bugs.python.org/issue30943> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30426] why not use the same style func name. eg: int.to_bytes (with underline) and array.tobytes(without underline).
zaazbb added the comment: how about add a unitive style function name, for a compatibility reason, keep the old function exists also. for example, add int.tobytes(), and keep int.to_bytes() exists. -- ___ Python tracker <http://bugs.python.org/issue30426> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com