Jack Diederich jackd...@gmail.com added the comment:
Marking closed/won't fix. ASCII strings are the byte-ish type in 2.x so
we should expect the caller to convert down from unicode when sending
bytes over the wire.
--
resolution: - wont fix
status: open - closed
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1772794
___
___
Jack Diederich jackd...@gmail.com added the comment:
assigning all open telnetlib items to myself
--
assignee: - jackdied
nosy: +jackdied
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1772794
sebek [EMAIL PROTECTED] added the comment:
I wonder if it is the same problem as bug #3725.
In this case it has been fixed in r66904 where telnetlib knows only
understand bytes instead of characters.
see http://bugs.python.org/issue3725
--
nosy: +sebek
Christian Heimes added the comment:
The code should raise a proper unicode error. In general network code
accepts only bytes, not unicode.
--
components: +Library (Lib) -None
nosy: +tiran
priority: normal - low
type: - rfe
versions: +Python 2.6
_
