summaryrefslogtreecommitdiffstats
path: root/Modules/arraymodule.c
Commit message (Collapse)AuthorAgeFilesLines
* Fixed the array module in unicode disabled build (regression of issue20014).Serhiy Storchaka2015-05-311-0/+2
|
* Issue #20014: array.array() now accepts unicode typecodes. Based on patch bySerhiy Storchaka2015-05-161-3/+15
| | | | Vajrasky Kok.
* Issue #15424: Add a __sizeof__ implementation for array objects.Meador Inge2012-08-111-0/+15
| | | | Patch by Ludwig Hähne.
* Fix docstring typo.Florent Xicluna2011-12-091-1/+1
|
* Reverted r87944 - issue #5109 should not have been backportedAlexander Belopolsky2011-01-111-16/+5
|
* Merged revisions 87942 via svnmerge fromAlexander Belopolsky2011-01-111-5/+16
| | | | | | | | | | | svn+ssh://pythondev@svn.python.org/python/branches/py3k ........ r87942 | alexander.belopolsky | 2011-01-11 16:44:00 -0500 (Tue, 11 Jan 2011) | 3 lines Issue #5109: array.array constructor will now use fast code when initial data is provided in an array object with correct type. ........
* Merged revisions 83751-83752 via svnmerge fromMark Dickinson2010-08-061-2/+2
| | | | | | | | | | | | | | svn+ssh://pythondev@svn.python.org/python/branches/py3k ........ r83751 | mark.dickinson | 2010-08-06 10:36:57 +0100 (Fri, 06 Aug 2010) | 1 line Issue #9526: Remove outdated casts to int that were preventing the array module from working correctly with arrays > 2GB. ........ r83752 | mark.dickinson | 2010-08-06 10:38:58 +0100 (Fri, 06 Aug 2010) | 1 line Misc/NEWS entry for r83751. ........
* Merged revisions 83030 via svnmerge fromAntoine Pitrou2010-07-211-2/+8
| | | | | | | | | | | | svn+ssh://pythondev@svn.python.org/python/branches/py3k ........ r83030 | antoine.pitrou | 2010-07-21 18:41:31 +0200 (mer., 21 juil. 2010) | 5 lines Issue #5395: check that array.fromfile() re-raises an IOError instead of replacing it with EOFError. (this is only an added test, but 2.x will get a fix too) ........
* Untabify C files. Will watch buildbots.Antoine Pitrou2010-05-091-1515/+1515
|
* Silence more 'comparison between signed and unsigned' warnings.Mark Dickinson2010-02-141-2/+2
|
* Issue #7788: Fix a crash produced by deleting a list slice with hugeMark Dickinson2010-01-291-2/+3
| | | | step value. Patch by Marcin Bachry.
* Issue #2389: Pickle array objects using a list representation for portabilityAlexandre Vassalotti2009-07-151-35/+33
| | | | across different machine architectures and compatibility with Python 3.x.
* Issue #5341: Fix a variety of spelling errors.Mark Dickinson2009-02-211-6/+6
|
* Issue #2620: Overflow checking when allocating or reallocating memoryGregory P. Smith2008-07-221-1/+4
| | | | | | | | was not always being done properly in some python types and extension modules. PyMem_MALLOC, PyMem_REALLOC, PyMem_NEW and PyMem_RESIZE have all been updated to perform better checks and places in the code that would previously leak memory on the error path when such an allocation failed have been fixed.
* Make more symbols static.Martin v. Löwis2008-06-131-1/+1
|
* Fix some memory dealloc problems when exceptions occur.Neal Norwitz2008-06-131-8/+7
| | | | It caused: "Fatal Python error: UNREF invalid object" in the DoubleTest.
* Merge in release25-maint r60793:Gregory P. Smith2008-06-111-1/+37
| | | | | | 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.
* This reverts r63675 based on the discussion in this thread:Gregory P. Smith2008-06-091-9/+9
| | | | | | | http://mail.python.org/pipermail/python-dev/2008-June/079988.html Python 2.6 should stick with PyString_* in its codebase. The PyBytes_* names in the spirit of 3.0 are available via a #define only. See the email thread.
* Renamed PyString to PyBytesChristian Heimes2008-05-261-9/+9
|
* A little reformating of Py3k warningsBenjamin Peterson2008-04-271-2/+2
|
* Use PyErr_WarnPy3k throughoutBenjamin Peterson2008-04-271-8/+4
|
* #2359: add Py3k warning for array.read/array.write.Georg Brandl2008-03-251-2/+26
|
* #1629: Renamed Py_Size, Py_Type and Py_Refcnt to Py_SIZE, Py_TYPE and ↵Christian Heimes2007-12-191-120/+120
| | | | Py_REFCNT. Macros for b/w compatibility are available.
* Improve extended slicing support in builtin types and classes. Specifically:Thomas Wouters2007-08-281-92/+136
| | | | | | | | | | | | | | | | | | | | - Specialcase extended slices that amount to a shallow copy the same way as is done for simple slices, in the tuple, string and unicode case. - Specialcase step-1 extended slices to optimize the common case for all involved types. - For lists, allow extended slice assignment of differing lengths as long as the step is 1. (Previously, 'l[:2:1] = []' failed even though 'l[:2] = []' and 'l[:2:None] = []' do not.) - Implement extended slicing for buffer, array, structseq, mmap and UserString.UserString. - Implement slice-object support (but not non-step-1 slice assignment) for UserString.MutableString. - Add tests for all new functionality.
* PEP 3123: Provide forward compatibility with Python 3.0, while keepingMartin v. Löwis2007-07-211-120/+118
| | | | | backwards compatibility. Add Py_Refcnt, Py_Type, Py_Size, and PyVarObject_HEAD_INIT.
* Array module's buffer interface can now handle empty arrays.Raymond Hettinger2007-04-021-0/+6
|
* SF #1693079: Cannot save empty array in shelveRaymond Hettinger2007-04-021-6/+13
|
* Bug #1486663: don't reject keyword arguments for subclasses of builtinGeorg Brandl2007-01-211-1/+1
| | | | types.
* Fix SF bug #1545837: array.array borks on deepcopy.Thomas Wouters2006-08-241-1/+1
| | | | | array.__deepcopy__() needs to take an argument, even if it doesn't actually use it. Will backport to 2.5 and 2.4 (if applicable.)
* Patch #1538606, Patch to fix __index__() clipping.Neal Norwitz2006-08-121-8/+4
| | | | | | | I modified this patch some by fixing style, some error checking, and adding XXX comments. This patch requires review and some changes are to be expected. I'm checking in now to get the greatest possible review and establish a baseline for moving forward. I don't want this to hold up release if possible.
* Klocwork made another run and found a bunch more problems.Neal Norwitz2006-08-121-0/+4
| | | | | | | This is the first batch of fixes that should be easy to verify based on context. This fixes problem numbers: 220 (ast), 323-324 (symtable), 321-322 (structseq), 215 (array), 210 (hotshot), 182 (codecs), 209 (etree).
* Patch #1495999: Part two of Windows CE changes.Martin v. Löwis2006-06-101-2/+2
| | | | | | - update header checks, using autoconf - provide dummies for getenv, environ, and GetVersion - adjust MSC_VER check in socketmodule.c
* Buffer objects would return the read or write buffer for a wrapped object whenBrett Cannon2006-06-081-0/+1
| | | | | | | | | the char buffer was requested. Now it actually returns the char buffer if available or raises a TypeError if it isn't (as is raised for the other buffer types if they are not present but requested). Not a backport candidate since it does change semantics of the buffer object (although it could be argued this is enough of a bug to bother backporting).
* Support for buffer protocol for socket and struct.Martin Blais2006-05-261-3/+3
| | | | | | | | | | * Added socket.recv_buf() and socket.recvfrom_buf() methods, that use the buffer protocol (send and sendto already did). * Added struct.pack_to(), that is the corresponding buffer compatible method to unpack_from(). * Fixed minor typos in arraymodule.
* C++ compiler cleanup: a cast here, a cast there... still does not compile ↵Skip Montanaro2006-04-181-3/+4
| | | | under C++ though...
* Use Py_VISIT in all tp_traverse methods, instead of traversing manually orThomas Wouters2006-04-151-2/+1
| | | | | | | | using a custom, nearly-identical macro. This probably changes how some of these functions are compiled, which may result in fractionally slower (or faster) execution. Considering the nature of traversal, visiting much of the address space in unpredictable patterns, I'd argue the code readability and maintainability is well worth it ;P
* Whitespace: break long lineNeal Norwitz2006-04-031-1/+2
|
* Checking in the code for PEP 357.Guido van Rossum2006-03-071-18/+11
| | | | | | This was mostly written by Travis Oliphant. I've inspected it all; Neal Norwitz and MvL have also looked at it (in an earlier incarnation).
* SF #1444030: Fix several potential defects found by Coverity.Hye-Shik Chang2006-03-071-4/+7
| | | | (reviewed by Neal Norwitz)
* Convert array.array.insert to use Py_ssize_t (like the rest already does.)Thomas Wouters2006-02-271-2/+2
|
* Bug #1432350: arrayobject should use PyObject_VAR_HEADGeorg Brandl2006-02-171-2/+1
|
* Use correct format specifier for Py_ssize_t variable to PyArg_ParseTuple().Thomas Wouters2006-02-161-1/+1
|
* Use Py_ssize_t for counts and sizes.Martin v. Löwis2006-02-161-16/+13
|
* Merge ssize_t branch.Martin v. Löwis2006-02-151-94/+99
|
* Check return result from Py_InitModule*(). This API can fail.Neal Norwitz2006-01-191-0/+2
| | | | Probably should be backported.
* Disallow keyword arguments for type constructors that don't use them.Georg Brandl2005-08-261-12/+3
| | | | (fixes bug #1119418)
* SF #1085304: Make array.array pickle-ableRaymond Hettinger2004-12-161-0/+25
|
* SF feature request #992967: array.array objects should support sequences.Raymond Hettinger2004-08-291-6/+20
| | | | Made the constructor accept general iterables.
* Add weakref support to array.array and file objects.Raymond Hettinger2004-05-311-2/+7
|
* SF feature request #686323: Minor array module enhancementsRaymond Hettinger2004-03-141-9/+34
| | | | | | | array.extend() now accepts iterable arguments implements as a series of appends. Besides being a user convenience and matching the behavior for lists, this the saves memory and cycles that would be used to create a temporary array object.
generated by cgit v0.12 at 2025-02-12 00:31:19 (GMT)