[issue2396] Backport memoryview object to Python 2.7

2009-04-02 Thread Antoine Pitrou
Antoine Pitrou added the comment: Committed in r71070. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Pyth

[issue2396] Backport memoryview object to Python 2.7

2009-03-13 Thread Antoine Pitrou
Antoine Pitrou added the comment: Here is an updated patch removing memory_str. I know Py_TPFLAGS_HAVE_NEWBUFFER should be documented, but I'm not sure where and how (I didn't add it in the first place). -- Added file: http://bugs.python.org/file13325/memview-trunk3.patch _

[issue2396] Backport memoryview object to Python 2.7

2009-02-21 Thread Benjamin Peterson
Benjamin Peterson added the comment: Some comments: - PyBytes_* API is fine. - memory_str should die. - Py_TPFLAGS_HAVE_NEWBUFFER needs to be documented. Otherwise it looks good. ___ Python tracker ___

[issue2396] Backport memoryview object to Python 2.7

2009-01-10 Thread Antoine Pitrou
Antoine Pitrou added the comment: This new patch includes documentation update and fixes as well. Added file: http://bugs.python.org/file12679/memview-trunk2.patch ___ Python tracker ___

[issue2396] Backport memoryview object to Python 2.7

2009-01-10 Thread Thomas Heller
Changes by Thomas Heller : -- nosy: +theller ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue2396] Backport memoryview object to Python 2.7

2009-01-10 Thread Antoine Pitrou
Antoine Pitrou added the comment: Here is a patch. Some remarks: - I had to disable a few tests in test_memoryview.py, mainly because array.array does not support the new buffer API in 2.x - I kept the PyBytes_* aliases in memoryobject.c rather than using the PyString_* equivalents. Is it ok? -