This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author beazley
Recipients beazley, georg.brandl
Date 2008-12-25.01:22:47
SpamBayes Score 7.019876e-05
Marked as misclassified No
Message-id <1230168171.56.0.381937953807.issue4744@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2008-12-25 01:22:52beazleysetrecipients: + beazley, georg.brandl
2008-12-25 01:22:51beazleysetmessageid: <1230168171.56.0.381937953807.issue4744@psf.upfronthosting.co.za>
2008-12-25 01:22:49beazleylinkissue4744 messages
2008-12-25 01:22:47beazleycreate