summaryrefslogtreecommitdiffstats
path: root/Objects/memoryobject.c
Commit message (Collapse)AuthorAgeFilesLines
* Issue #14181: Preserve backwards compatibility for getbufferprocs that a) doStefan Krah2012-03-051-1/+1
| | | | | not adhere to the new documentation and b) manage to clobber view->obj before returning failure.
* Issue #14181: Allow memoryview construction from an object that uses theStefan Krah2012-03-051-3/+0
| | | | getbuffer redirection scheme.
* - Issue #10181: New memoryview implementation fixes multiple ownershipStefan Krah2012-02-251-563/+2302
| | | | | | | | | | | | | | | | | | and lifetime issues of dynamically allocated Py_buffer members (#9990) as well as crashes (#8305, #7433). Many new features have been added (See whatsnew/3.3), and the documentation has been updated extensively. The ndarray test object from _testbuffer.c implements all aspects of PEP-3118, so further development towards the complete implementation of the PEP can proceed in a test-driven manner. Thanks to Nick Coghlan, Antoine Pitrou and Pauli Virtanen for review and many ideas. - Issue #12834: Fix incorrect results of memoryview.tobytes() for non-contiguous arrays. - Issue #5231: Introduce memoryview.cast() method that allows changing format and shape without making a copy of the underlying memory.
* Issue #13411: memoryview objects are now hashable when the underlying object ↵Antoine Pitrou2011-11-211-1/+33
| | | | is hashable.
* Replace Py_NotImplemented returns with the macro form Py_RETURN_NOTIMPLEMENTED.Brian Curtin2011-08-111-2/+1
| | | | The macro was introduced in #12724.
* Issue #11286: Raise a ValueError from calling PyMemoryView_FromBuffer withAntoine Pitrou2011-02-241-0/+5
| | | | a buffer struct having a NULL data pointer.
* Issue #10451: memoryview objects could allow to mutate a readable buffer.Antoine Pitrou2011-01-181-3/+0
| | | | Initial patch by Ross Lagerwall.
* Merge branches/pep-0384.Martin v. Löwis2010-12-031-2/+2
|
* Issue #10293: Remove obsolete field in the PyMemoryView structure,Antoine Pitrou2010-11-041-44/+1
| | | | | unused undocumented value PyBUF_SHADOW, and strangely-looking code in PyMemoryView_GetContiguous.
* deuglifyBenjamin Peterson2010-11-031-2/+3
|
* Issue #9757: memoryview objects get a release() method to release theAntoine Pitrou2010-09-091-10/+75
| | | | | underlying buffer (previously this was only done when deallocating the memoryview), and gain support for the context management protocol.
* Fix a compilation warningAntoine Pitrou2010-09-011-1/+1
|
* Issue #9737: Fix a crash when trying to delete a slice or an item fromAntoine Pitrou2010-09-011-0/+5
| | | | a memoryview object.
* Issue #3101: Helper functions _add_one_to_C() and _add_one_to_F() becomeAntoine Pitrou2010-09-011-5/+2
| | | | _Py_add_one_to_C() and _Py_add_one_to_F(), respectively.
* Issue #2443: Added a new macro, Py_VA_COPY, which is equivalent to C99Alexander Belopolsky2010-08-111-4/+4
| | | | | va_copy, but available on all python platforms. Untabified a few unrelated files.
* Issue #7616: Fix copying of overlapping memoryview slices with the IntelAntoine Pitrou2010-07-111-11/+3
| | | | compiler.
* Merged revisions 77916 via svnmerge fromAntoine Pitrou2010-02-021-7/+5
| | | | | | | | | | | svn+ssh://pythondev@svn.python.org/python/trunk ........ r77916 | antoine.pitrou | 2010-02-02 23:36:17 +0100 (mar., 02 févr. 2010) | 4 lines Issue #7385: Fix a crash in `MemoryView_FromObject` when `PyObject_GetBuffer` fails. Patch by Florent Xicluna. ........
* Slightly improve buffer-related error message.Georg Brandl2009-08-041-1/+1
|
* Issue 6329: Fix iteration for memoryviews.Raymond Hettinger2009-06-231-32/+51
|
* remove memoryview.__str__ #5182Benjamin Peterson2009-02-081-17/+1
|
* Issue #1717: rename tp_compare to tp_reserved. I'll change theMark Dickinson2009-02-021-1/+1
| | | | | type of tp_compare in a separate commit, for ease of reversion should things go wrong.
* Issue #4822: fix messy indentation in memoryobject.c/.h, before we may ↵Antoine Pitrou2009-01-031-432/+431
| | | | | | backport it to trunk. Reviewed on IRC by Georg Brandl, with assistance by Benjamin Peterson.
* Issue #4580: slicing of memoryviews when itemsize != 1 is wrong.Antoine Pitrou2009-01-031-68/+63
| | | | | | | | Also fix len() to return number of items rather than length in bytes. I'm sorry it was not possible for me to work on this without reindenting a bit some stuff around. The indentation in memoryobject.c is a mess, I'll open a separate bug for it.
* Issue #4569: Interpreter crash when mutating a memoryview with an item size ↵Antoine Pitrou2008-12-071-93/+105
| | | | | | larger than 1. (together with a bit of reindenting)
* kill memoryview.size in favor of len(view)Benjamin Peterson2008-09-101-7/+0
| | | | Reviewer: Antoine Pitrou #3827
* #3712: The memoryview object had a reference leak and didn't support cyclic ↵Antoine Pitrou2008-09-011-34/+66
| | | | | | garbage collection. Reviewed by Benjamin Peterson.
* Issue #2394: implement more of the memoryview API.Antoine Pitrou2008-08-191-22/+220
|
* #3560: cleanup C memoryview APIAntoine Pitrou2008-08-191-3/+3
|
* Merged revisions 65654 via svnmerge fromMartin v. Löwis2008-08-131-15/+18
| | | | | | | | | | | | | | svn+ssh://pythondev@svn.python.org/python/trunk ........ r65654 | martin.v.loewis | 2008-08-12 16:49:50 +0200 (Tue, 12 Aug 2008) | 6 lines Issue #3139: Make buffer-interface thread-safe wrt. PyArg_ParseTuple, by denying s# to parse objects that have a releasebuffer procedure, and introducing s*. More module might need to get converted to use s*. ........
* #2538: bytes objects can only provide read-only buffersAntoine Pitrou2008-08-021-5/+5
|
* Merged revisions 64114 via svnmerge fromAmaury Forgeot d'Arc2008-06-181-1/+4
| | | | | | | | | | | | | | svn+ssh://pythondev@svn.python.org/python/trunk ........ r64114 | gregory.p.smith | 2008-06-11 09:41:16 +0200 (mer., 11 juin 2008) | 6 lines Merge in release25-maint r60793: Added checks for integer overflows, contributed by Google. Some are only available if asserts are left in the code, in cases where they can't be triggered from Python code. ........
* Remove locking from buffer protocol as-per discussion.Travis E. Oliphant2008-06-061-3/+0
|
* Renamed PyBytes to PyByteArrayChristian Heimes2008-05-261-6/+6
|
* Cleanup: Replaced most PyInt_ aliases with PyLong_ and disabled the aliases ↵Christian Heimes2007-12-021-4/+4
| | | | in intobject.h
* Fixed memoryview constructor. It allowed arbitrary keyword arguments. The ↵Christian Heimes2007-11-081-3/+8
| | | | bug was found by mykhal from #python. I've also added a small test case in the new test_memoryview.py
* Fix some Py_ssize_t warnings on Win64 that were probably bugsNeal Norwitz2007-10-261-2/+2
|
* Fix problems with memoryview object. There is still more to do to finish ↵Travis E. Oliphant2007-10-121-7/+19
| | | | PEP 3118. The memory-view object needs to be fleshed out and the struct module needs to be modified.
* Delete bufferobject.[ch].Guido van Rossum2007-10-081-1/+4
| | | | This will undoubtedly require Windows build file changes too.
* At least one of the buildbots was complaining about newview being usedNeal Norwitz2007-10-071-3/+2
| | | | | without being initialized. Also make the code conform to the comment and return the new object. This code needs a test!
* Whitespace and line lengrth cleanup.Guido van Rossum2007-09-251-47/+50
|
* Change PyBuffer to Py_buffer to be consistent with other non-object ↵Travis E. Oliphant2007-09-231-13/+72
| | | | structures like Py_complex. Add some more functionality to the memoryview object.
* Fixing the spelling of "writeable" to "writable", particularly PyBUF_WRITEABLE.Sean Reifscheider2007-09-171-3/+3
|
* SF #1777057, fix memoryview('test') so it works in debug mode too.Neal Norwitz2007-08-191-30/+18
| | | | | | | Also return a boolean for the readonly flag. Other cleanup: make sure to set an exception when returning NULL and reformat the getsets to be shorter by putting them all on one line.
* Code review of the new buffer protocol. Mostly add questions that shouldNeal Norwitz2007-08-191-16/+13
| | | | | | | | | | | be answered with the comments removed. There are many places that require checks when doing arithmetic for memory sizes when allocating memory. Otherwise, overflow is possible with a subsequent crash. Fix SF #1777057 which was a result of not initializing the new BufferError properly. Had to update the test for exceptions for BufferError too.
* Merged in py3k-buffer branch to main line. All objects now use the buffer ↵Travis E. Oliphant2007-08-181-0/+540
protocol in PEP 3118.
generated by cgit v0.12 at 2024-10-03 21:38:45 (GMT)