[New-bugs-announce] [issue4744] asynchat documentation needs to be more precise

[David M. Beazley]

New submission from David M. Beazley <beazley at users.sourceforge.net>:

The documentation for asynchat needs to be more precise in its use of 
strings vs. bytes.   Unless the undocumented use_encoding attribute is 
set, it seems that all data should be bytes throughout (e.g., the 
terminator, inputs to push methods, etc.).  

I have no idea if the use_encoding attribute is officially blessed or 
not.  However, to avoid "magic behavior", I'm guessing that it would be 
better practice to be explicit in one's use of bytes vs. text rather 
than having take place in the internals of asynchat.   Advice welcome.

----------
assignee: georg.brandl
components: Documentation
messages: 78277
nosy: beazley, georg.brandl
severity: normal
status: open
title: asynchat documentation needs to be more precise
versions: Python 3.0

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue4744>
_______________________________________