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 teoliphant
Recipients amaury.forgeotdarc, ncoghlan, pitrou, teoliphant
Date 2008-12-10.15:05:03
SpamBayes Score 7.727535e-06
Marked as misclassified No
Message-id <1228921505.12.0.74177803214.issue4580@psf.upfronthosting.co.za>
In-reply-to
Content
I will take some time in the next week to look at this issue.  Thank you
for bringing these bugs to my attention.  

I did not finish the memoryview implementation, due to other demands on
my time.  I appreciate the efforts of so many to pick up and understand
the PEP and contribute code.   I've noticed some incorrect statements
being passed around, and I apologize for not providing a perspective on
them.   

I hope there is a clear distinction between the buffer protocol and the
memoryview object.   The buffer protocol was thought through fairly
well, but the memoryview object has not received the same attention.  My
mental model of the memoryview object is basically an (enhanced) NumPy
array without the math support.  

It does not suprise me that there are a few remaining issues in the
memoryview object.  However, I'm confident they can be cleared up.   A
few changes to the code were made by others without changing the PEP.  I
accept responsibility for this because people were cleaning up what I
should have already finished.  

All the help is appreciated.  I will review the patches and fix the
problem.
History
Date User Action Args
2008-12-10 15:05:05teoliphantsetrecipients: + teoliphant, amaury.forgeotdarc, ncoghlan, pitrou
2008-12-10 15:05:05teoliphantsetmessageid: <1228921505.12.0.74177803214.issue4580@psf.upfronthosting.co.za>
2008-12-10 15:05:04teoliphantlinkissue4580 messages
2008-12-10 15:05:03teoliphantcreate