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 giampaolo.rodola
Recipients georg.brandl, giampaolo.rodola, josiahcarlson, lehmannro
Date 2010-04-26.23:20:13
SpamBayes Score 4.9527907e-06
Marked as misclassified No
Message-id <1272324015.3.0.403174320578.issue6916@psf.upfronthosting.co.za>
In-reply-to
Content
I seem to remember that those classes were initially removed and then re-added by Josiah for backward compatibility (see discussions in issue 1641 and issue 1736190).

Despite practically useless after the changes applied to asynchat in Python 2.6, both classes are there since the very first checkin of asynchat.py, and the common policy in this case is to grant compatibility with older code, just in case few person out of many still rely on it.

I'd be more for stopping to mention them in the documentation, also because now that I look at it, the doc is wrong as it claims that "Each channel maintains a fifo" while this is no longer true since fifo() has been replaced by a deque().
History
Date User Action Args
2010-04-26 23:20:15giampaolo.rodolasetrecipients: + giampaolo.rodola, georg.brandl, josiahcarlson, lehmannro
2010-04-26 23:20:15giampaolo.rodolasetmessageid: <1272324015.3.0.403174320578.issue6916@psf.upfronthosting.co.za>
2010-04-26 23:20:13giampaolo.rodolalinkissue6916 messages
2010-04-26 23:20:13giampaolo.rodolacreate