classification
Title: asynchat documentation needs to be more precise
Type: Stage: needs patch
Components: Documentation Versions: Python 3.2, Python 3.1, Python 2.7
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: docs@python Nosy List: BreamoreBoy, beazley, docs@python, georg.brandl, giampaolo.rodola, josiah.carlson
Priority: normal Keywords:

Created on 2008-12-25 01:22 by beazley, last changed 2010-07-31 11:35 by BreamoreBoy.

Messages (2)
msg78277 - (view) Author: David M. Beazley (beazley) Date: 2008-12-25 01:22 
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.
msg112137 - (view) Author: Mark Lawrence (BreamoreBoy) Date: 2010-07-31 11:35 
Is there anyone with knowledge of asynchat who could provide a patch for this?
History
Date User Action Args
2010-07-31 11:35:49BreamoreBoysetversions: + Python 3.1, Python 2.7, Python 3.2, - Python 3.0
nosy: + BreamoreBoy, docs@python

messages: + msg112137

assignee: georg.brandl -> docs@python
stage: needs patch
2008-12-27 02:41:46giampaolo.rodolasetnosy: + giampaolo.rodola, josiah.carlson
2008-12-25 01:22:50beazleycreate