➜

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 neologix
Recipients giampaolo.rodola, josiah.carlson, josiahcarlson, neologix, pitrou, xdegaye
Date 2012-12-28.21:45:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM2bj6e+euG2=ALFi8RZkfCpsrG93S=oDg6Yes=gEHewbw@mail.gmail.com>
In-reply-to <1356722824.27.0.586322176027.issue16787@psf.upfronthosting.co.za>
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.

Probably.
For an example of how it might be used, you can have a look here:
http://stackoverflow.com/questions/6736771/buffers-and-memoryview-objects-explained-for-the-non-c-programmer
and here:
http://eli.thegreenplace.net/2011/11/28/less-copies-in-python-with-the-buffer-protocol-and-memoryviews/

Also, IIRC, Antoine used memoryviews when rewriting parts of
multiprocessing in pure Python.
History
Date User Action Args
2012-12-28 21:45:28neologixsetrecipients: + neologix, josiahcarlson, pitrou, giampaolo.rodola, josiah.carlson, xdegaye
2012-12-28 21:45:28neologixlinkissue16787 messages
2012-12-28 21:45:28neologixcreate