[issue5414] asciibin.a2b_uu returns unexpected values on non ascii data

[David Majnemer]

New submission from David Majnemer :

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.

--
components: Library (Lib)
messages: 83114
nosy: dmajnemer
severity: normal
status: open
title: asciibin.a2b_uu returns unexpected values on non ascii data
type: behavior

___
Python tracker 
<http://bugs.python.org/issue5414>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue5414] asciibin.a2b_uu returns unexpected values on non ascii data

[David Majnemer]

David Majnemer  added the comment:

Added version number of python.

--
versions: +Python 2.5

___
Python tracker 
<http://bugs.python.org/issue5414>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue5416] str.replace does strange things when given a negative count

[David Majnemer]

New submission from David Majnemer :

str.replace("", "", "asdf", -1) returns "asdf", I believe this is not
correct and strictly speaking not up to the documentation posted. I am
of the opinion that it should function like str.replace("", "", "asdf",
0) which returns ""

--
components: Interpreter Core
messages: 83119
nosy: dmajnemer
severity: normal
status: open
title: str.replace does strange things when given a negative count
versions: Python 2.5

___
Python tracker 
<http://bugs.python.org/issue5416>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com