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 BreamoreBoy, docs@python, ezio.melotti, georg.brandl, giampaolo.rodola, josiahcarlson, lehmannro, python-dev, rhettinger
Date 2014-06-21.12:01:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1403352113.83.0.713647320564.issue6916@psf.upfronthosting.co.za>
In-reply-to
Content
Signaling the deprecation or just the existence of asynchat.fifo really isn't worth the effort because the code is no longer used since fifo was replaced with a deque in python 2.6.
Basically it's dead code and the only reason it remained there is because there were some complaints about a compatibility breakage when the 2.6 patch was applied, but I remember fifo class had nothing to do with it.
FWIW I added a deprecation warning and scheduled asynchat.fifo for removal in python 3.6 but IMO it is not worth it to mention it in the doc.
History
Date User Action Args
2014-06-21 12:01:53giampaolo.rodolasetrecipients: + giampaolo.rodola, georg.brandl, rhettinger, josiahcarlson, lehmannro, ezio.melotti, docs@python, BreamoreBoy, python-dev
2014-06-21 12:01:53giampaolo.rodolasetmessageid: <1403352113.83.0.713647320564.issue6916@psf.upfronthosting.co.za>
2014-06-21 12:01:53giampaolo.rodolalinkissue6916 messages
2014-06-21 12:01:53giampaolo.rodolacreate