delta/python-packages/numpy.git/numpy/numarray/_capi.c, branch dependabot/pip/gitpython-3.1.14 github.com: numpy/numpy.git DEP: Remove deprecated modules numarray and oldnumeric. 2013-09-23T21:11:12+00:00 Charles Harris charlesr.harris@gmail.com 2013-08-19T00:40:28+00:00 3beebbc0164afbbcc2b6840cf56174c6c073bb40 They were deprecated in 1.8 and scheduled for removal in 1.9. Closes #3637. 
They were deprecated in 1.8 and scheduled for removal in 1.9.

Closes #3637.
FIX: remove unused variables and add casts 2013-08-27T10:17:25+00:00 Lars Buitinck L.J.Buitinck@uva.nl 2013-08-27T10:05:22+00:00 994bf25181ad33385dcd7f6615846f98f06e6f3e Makes the build complete with fewer warnings. 
Makes the build complete with fewer warnings.
MAINT: Remove outdated version checks. 2013-07-11T18:43:18+00:00 Charles Harris charlesr.harris@gmail.com 2013-07-11T18:08:49+00:00 28eadc0e31ca7aea5c679023d1e703856f45c879 Because Numpy 1.8.0 will no longer supports Python versions < 2.6 we no longer need to check for that and can also remove the code that is specific to those earlier versions. To make this a bit safer, the toplevel setup.py file now contains a check of the Python version number and raises an error when run by an unsupported version. 
Because Numpy 1.8.0 will no longer supports Python versions < 2.6 we
no longer need to check for that and can also remove the code that is
specific to those earlier versions.

To make this a bit safer, the toplevel setup.py file now contains a
check of the Python version number and raises an error when run by an
unsupported version.
Use PyMODINIT_FUNC and update docs accordingly. 2012-09-03T06:53:15+00:00 cgohlke cgohlke@uci.edu 2012-08-05T21:17:30+00:00 ead9e09c5adbc94bfc3c5cc8344089b836cfffd5 See https://github.com/scipy/scipy/pull/279 
See https://github.com/scipy/scipy/pull/279
Rename PyArray_RequireWriteable to PyArray_FailUnlessWriteable 2012-05-22T10:19:11+00:00 Nathaniel J. Smith njs@pobox.com 2012-05-22T10:16:48+00:00 51616c9265155f75e536ba19c32f9f91337243af Also clean up its API slightly so that the caller passes in a name describing the array being checked which is used to generate an error message, rather than writing an error message from scratch. 
Also clean up its API slightly so that the caller passes in a name
describing the array being checked which is used to generate an error
message, rather than writing an error message from scratch.
Funnel all assignments to PyArrayObject->base through a single point 2012-05-15T17:48:08+00:00 Nathaniel J. Smith njs@pobox.com 2012-05-15T17:32:14+00:00 6a90adaea6ba4330e8da4db546425d9cdcc5a940 This patch removes all direct assignments of non-NULL values to the 'base' field on PyArrayObjects. A new utility function was created to set up UPDATEIFCOPY arrays, and all assignments to 'base' were adjusted to use either PyArray_SetBaseObject or the new PyArray_SetUpdateIfCopyBase. One advantage of this is that it produces more consistent error handling. This error handling revealed a bug in the nditer code, which this patch does *not* yet fix. The bug is that npyiter_new_temp_array sometimes (when dealing with reversed axes) creates an array and then returns a view onto it. But, npyiter_allocate_arrays assumes that the array returned by npyiter_new_temp_array can have UPDATEIFCOPY set, which requires reassigning its 'base' field. Previously, this meant that the temporary array leaked. Now, it produces a ValueError. This code path doesn't seem to actually be hit very often; only one of the nditer tests fails because of the change. See numpy/core/tests/test_nditer.py:test_iter_array_cast_buggy 
This patch removes all direct assignments of non-NULL values to the
'base' field on PyArrayObjects. A new utility function was created to
set up UPDATEIFCOPY arrays, and all assignments to 'base' were
adjusted to use either PyArray_SetBaseObject or the new
PyArray_SetUpdateIfCopyBase.

One advantage of this is that it produces more consistent error
handling. This error handling revealed a bug in the nditer code,
which this patch does *not* yet fix.

The bug is that npyiter_new_temp_array sometimes (when dealing with
reversed axes) creates an array and then returns a view onto it. But,
npyiter_allocate_arrays assumes that the array returned by
npyiter_new_temp_array can have UPDATEIFCOPY set, which requires
reassigning its 'base' field. Previously, this meant that the
temporary array leaked. Now, it produces a ValueError.

This code path doesn't seem to actually be hit very often; only one of
the nditer tests fails because of the change. See
   numpy/core/tests/test_nditer.py:test_iter_array_cast_buggy
Consolidate all array writeability checking in new PyArray_RequireWriteable 2012-05-15T14:02:24+00:00 Nathaniel J. Smith njs@pobox.com 2012-05-14T22:43:45+00:00 cbce4e6565e7a7fbe065502b264622ce7d64740a This is mostly a code cleanup, but it does have a user-visible effect in that attempting to write to a unwriteable array now consistently raises ValueError. (It used to randomly raise either ValueError or RuntimeError.) Passes numpy.test("full"). 
This is mostly a code cleanup, but it does have a user-visible effect
in that attempting to write to a unwriteable array now consistently
raises ValueError. (It used to randomly raise either ValueError or
RuntimeError.)

Passes numpy.test("full").
DEP: Update all the '#define NPY_NO_DEPRECATED_API' instances to be 2012-04-06T21:54:30+00:00 Mark Wiebe mwwiebe@gmail.com 2012-02-05T00:28:28+00:00 e1218cc68ddab6b806628877de19394616df04f7 versioned 
versioned
UPDATE: Replace macros in old_defines.h by new. 2012-02-04T23:11:39+00:00 Charles Harris charlesr.harris@gmail.com 2012-02-02T01:42:25+00:00 8a0e7cd26ea2803b8580dcca1d1306baa1d702dc With the exception of the numarray fixups these were all instances that were results of code generation. 
With the exception of the numarray fixups these were all instances
that were results of code generation.
ENH: core: Rename PyArray_SetBase to PyArray_SetBaseObject to be more clear 2011-07-22T20:40:28+00:00 Mark Wiebe mwiebe@enthought.com 2011-07-22T20:40:28+00:00 a2ed62a5f42459a14c233cef35f07a032c9ca36c