[issue16995] Add Base32 support for RFC4648 "Extended Hex" alphabet (patch attached)

2013-01-18 Thread Matthäus Wander
New submission from Matthäus Wander: RFC4648 specifies two different alphabets for Base32: 1) the common one already used in RFC3548 and implemented in Python, and 2) an "Extended Hex" alphabet which is used by e.g. DNSSEC NSEC3 but not yet implemented in Python. The attached patch

[issue16995] Add Base32 support for RFC4648 "Extended Hex" alphabet (patch attached)

2013-01-18 Thread Matthäus Wander
Matthäus Wander added the comment: Added single patch as requested. -- keywords: +patch Added file: http://bugs.python.org/file28772/py3_base32hex.patch ___ Python tracker <http://bugs.python.org/issue16

[issue16995] Add Base32 support for RFC4648 "Extended Hex" alphabet (patch attached)

2015-07-22 Thread Matthäus Wander
Matthäus Wander added the comment: I've created a new patch that works against the current 3.5 sources. Should be fine for 3.6, I guess. Separate functions b32hexencode and b32hexdecode are used now. There is no optional parameter "base32hex" anymore. -- versions: +Pyt

[issue16995] Add Base32 support for RFC4648 "Extended Hex" alphabet (patch attached)

2015-07-23 Thread Matthäus Wander
Matthäus Wander added the comment: *facepalm* Yes, I uploaded the old patch twice. Sorry for that. - Added doc update. - Added test case that includes all 32 characters codes. I'm reusing the existing Base32 table generation logic without changes. It has been changed (in 3.4 or so) sinc