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 giampaolo.rodola, josiah.carlson, josiahcarlson, neologix, pitrou, xdegaye
Date 2012-12-28.19:27:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1356722824.27.0.586322176027.issue16787@psf.upfronthosting.co.za>
In-reply-to
Content
> memoryview is also great to avoid copies when sending/receiving to a socket.

That's interesting. How exactly? Would producer_fifo have to change from a deque() to a memoryview() object? In that case we might have to take backward compatibility into account (producer_fifo already changed in 2.6 and if I'm not mistaken that might have caused some problems).
Maybe it makes sense to file a separate issue to address asynchat enhancements.
History
Date User Action Args
2012-12-28 19:27:04giampaolo.rodolasetrecipients: + giampaolo.rodola, josiahcarlson, pitrou, josiah.carlson, neologix, xdegaye
2012-12-28 19:27:04giampaolo.rodolasetmessageid: <1356722824.27.0.586322176027.issue16787@psf.upfronthosting.co.za>
2012-12-28 19:27:04giampaolo.rodolalinkissue16787 messages
2012-12-28 19:27:04giampaolo.rodolacreate