classification
Title: asciibin.a2b_uu returns unexpected values on non ascii data
Type: behavior Stage: test needed
Components: Library (Lib) Versions: Python 2.5
process
Status: closed Resolution: out of date
Dependencies: Superseder:
Assigned To: Nosy List: dmajnemer, terry.reedy
Priority: normal Keywords:

Created on 2009-03-04 05:16 by dmajnemer, last changed 2010-08-03 19:27 by terry.reedy. This issue is now closed.

Messages (3)
msg83114 - (view) Author: David Majnemer (dmajnemer) Date: 2009-03-04 05:16
Note that binascii.a2b_uu("\0") returns
'\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'.
This appears to be the same as binascii.a2b_uu() which is most likely
not the intention.
Also, binascii.a2b_uu("\0\0") returns an exception, "Illegal char",
which makes sense.
msg83115 - (view) Author: David Majnemer (dmajnemer) Date: 2009-03-04 05:18
Added version number of python.
msg112654 - (view) Author: Terry J. Reedy (terry.reedy) * (Python committer) Date: 2010-08-03 19:27
In 3.1.2, a2b_uu() now raises
TypeError: a2b_uu() takes exactly 1 argument (0 given)
as it should. I assume the same of 2.7.
The manual claims, in effect, that a2b_uu(b2a_uu(data))== data.
The behavior of a2b_uu with any other input (not from b2a_uu) seems to be undefined.
History
Date User Action Args
2010-08-03 19:27:32terry.reedysetstatus: open -> closed

nosy: + terry.reedy
messages: + msg112654

resolution: out of date
stage: test needed
2009-03-04 05:18:57dmajnemersetmessages: + msg83115
versions: + Python 2.5
2009-03-04 05:16:47dmajnemercreate