[issue17145] memoryview(array.array)

Stefan Krah added the comment: I pushed a minimal patch that focuses on the array.array issue. For broader changes, I suggest to use #14198 (though it is unlikely tha anyone will work on it). -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___

[issue17145] memoryview(array.array)

Roundup Robot added the comment: New changeset 0a2ac61729d2 by Stefan Krah in branch '2.7': Issue #17145: Document array.array buffer interface limitations. http://hg.python.org/cpython/rev/0a2ac61729d2 -- nosy: +python-dev ___ Python tracker

[issue17145] memoryview(array.array)

Changes by Paul Sokolovsky : -- nosy: +pfalcon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyt

[issue17145] memoryview(array.array)

Changes by mpb : -- nosy: +mpb ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/

[issue17145] memoryview(array.array)

Stefan Krah added the comment: The request is certainly valid, but the patch is tricky to review. -- ___ Python tracker ___ ___ Python

[issue17145] memoryview(array.array)

Demian Brecht added the comment: Bump. If the patch (or request) is invalid, might be worthwhile closing this issue (although I still think it's valid ;)). -- ___ Python tracker ___

[issue17145] memoryview(array.array)

Demian Brecht added the comment: Yes, I agree that passage is a little garbled. I've reworked that particular paragraph in the new patch. I had included a little information about 2.6 as it was in the revision prior to my patch (and there was also some historical context back to 1.6). I think

[issue17145] memoryview(array.array)

Terry J. Reedy added the comment: I am looking at this as a naive user, and can only assume that the claims are correct. +The new C-level buffer API has been backported to Python 2.6 and the +Python-level :class:`memoryview` object has been backported to Python 2.7. +To be clear, in Python 2.6

[issue17145] memoryview(array.array)

Demian Brecht added the comment: I've given this some more thought and quite a bit more work and reorganization. I think this clarifies the usage of memoryviews and buffers as well as the C-level API for each. This is my first run at contributing a patch of any sort, so please let me know if

[issue17145] memoryview(array.array)

Demian Brecht added the comment: Strike that patch, this needs a little more love than during-my-first-coffee-of-the-day work. I'll work on it more and submit a follow-up for review. -- ___ Python tracker ___

[issue17145] memoryview(array.array)

Demian Brecht added the comment: Here's a patch for the docs that adds a little clarity. -- keywords: +patch Added file: http://bugs.python.org/file28986/buffer.patch ___ Python tracker

[issue17145] memoryview(array.array)

Stefan Krah added the comment: Changing array.array would be a new feature, so it cannot go into 2.7. The documentation could be improved, see also #14198. -- assignee: -> docs@python components: +Documentation -None nosy: +docs@python, skrah ___ Py

[issue17145] memoryview(array.array)

New submission from Demian Brecht: array.array doesn't implement the buffer interface in 2.7, so memoryviews cannot be applied to them. As memoryview has been backported to 2.7, array.array should be updated to support it. Either that, or the 2.7 documentation should be updated to reflect the