| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
declarations
The problem this fix resolves is to ensure that 32-bit and 64-bit functions
(e.g., fclear() and fclear64()) to access/manipulate "large files" are
defined properly - much as GNU and other platforms use one or more of
the defines _FILE_OFFSET_BITS, _LARGEFILE_SOURCE, and _LARGEFILE64_SOURCE.
Without this fix the numpy code only defines flags that are not recognized
in the AIX environment and have no effect in anyway.
The fix applies the AIX convention and does not "export" any of the flags
currently exported. For all other platforms the current flags:
_FILE_OFFSET_BITS, _LARGEFILE_SOURCE, and _LARGEFILE64_SOURCE are "exported".
This fix should not have any impact or side-effect based on the version
of python used.
History:
Starting around 1997 AIX started supporting so-called "large files",
i.e., length > signed 32-bit. In the period 1997-1998 the flag _LARGE_FILES
was established to simplify porting 32-bit applications to 64-bit.
The convention is to define _LARGE_FILES before including any
"system include files" either as an argument to ${CC} (e.g., in ${CFLAGS}
or as the first #define in every source file. This is to ensure that
that no relevant function calls would be redefined later in the build process.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The cause of issue #5692 is that `_array2string` (in
numpy/core/arrayprint.py) doesn’t have format function for structured
arrays and it uses general purpose format function to format array
elements of structured arrays.
This commit adds `StructureFormat` class to format structured array
elements. `_get_format_function` instantiates `StructureFormat` by
instantiating format function classes for each field of structure
recursively and merge them.
Closes #5692.
|
| |
|
|\
| |
| | |
MAINT: Expose void-scalar "base" attribute in python
|
| | |
|
| |
| |
| |
| |
| |
| | |
OSX 10.11 ships a clang that uses it but does not implement the necesary
library function
closes gh-8130
|
|/
|
|
|
|
| |
some people use new compilers with old linkers so the target attribute
check for AVX is not enough
closes gh-8128
|
|\
| |
| | |
Pypy fixes
|
| |
| |
| |
| | |
overriding function pointers
|
| | |
|
|\ \
| | |
| | | |
Rebase, BUG: Fixed deepcopy of F-order object arrays.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Values rounding to zero were formatted with negative precision.
|
|/ / |
|
| | |
|
|\ \
| | |
| | | |
ENH: Add ability to runtime select ufunc loops, add AVX2 integer loops
|
| | | |
|
| | |
| | |
| | |
| | | |
Selected at runtime depending on CPU features.
|
| | | |
|
| | |
| | |
| | |
| | | |
NPY_CPU_SUPPORTS_AVX2 checks at runtime if AVX2 is supported
|
|\ \ \
| | | |
| | | | |
WIP: MAINT: Add deprecation warning to views of multi-field indexes
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Behavior of multi-field indexes will change in 1.13: Multi-field indexes
will return a view (not a copy) and assignment between structures with
non-identical fieldnames occurs "by position" (not "by fieldname"):
>>> a = zeros(10, dtype=[('x', 'i8'), ('y', 'i8'), ('z', 'i8')])
>>> a[['x', 'z']].view('i4') # Deprecation warning for multifield view
>>> b = ones(10, dtype=[('y', 'i4'), ('x', 'f4')])
>>> a[:] = b # Deprecation warning for multifield assignment
|
|/ /
| |
| |
| |
| | |
Fix is to convert offsets to python ints at dtype creation.
Fixes #8059
|
|\ \
| | |
| | | |
Clear signaling NaN exceptions
|
| | |
| | |
| | |
| | | |
Closes gh-7838
|
|\ \ \
| |/ /
|/| | |
ENH: a.resize(.., refcheck=True) is almost unusable on PyPy
|
| | | |
|
|\ \ \
| |/ /
|/| | |
MAINT: Update error message in rollaxis.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Updates error message to properly reflect
that the 'start' or 'axis' can be negative.
Closes gh-7974.
|
|/ /
| |
| |
| |
| |
| | |
It is possible to skip copying an array to the buffer only if the
reduction outer iterator is 1-dimensional --- the array may not be
c-contiguous.
|
| | |
|
| | |
|
| |
| |
| |
| | |
The strings in error messages were left untouched
|
| |
| |
| |
| |
| |
| |
| | |
There were two remaining imports of the deprecated imp module, neither
of which seems to have been used beyond the import.
Closes #5997.
|
| | |
|
|\ \
| | |
| | | |
Suppressed warnings
|
| | |
| | |
| | |
| | |
| | | |
These are warnings, which when raised as an error for one reason
or another are already silenced.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In some places, just remove aparently unnecessary filters.
After this, all cases of ignore filters should be removed from
the tests, making testing (even multiple runs) normally fully
predictable.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Printing of datetime arrays used to cause warning due to
comparison warnings in NaT. This is circumvented by using views
to integer values. Part of this should be simplified when
the deprecation is over.
Also fixes a bug with non-native byteorder.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Due to the lambdas used it didn't actually generate inplace cases.
Fix a few tests that now break due to assuming that the cases are always
out of place.
Also update some numbers to make it more likely to find issues like
loading from wrong array.
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
Both gcc and clang don't automatically specialize the inplace case, so
add extra conditions to the loop macros to get the compilers to emit
decent code.
Without them inplace code ends up much slower than the out of place
code.
|
|\ \
| |/
|/| |
BUG: Fixed masked array behavior for scalar inputs to np.ma.atleast_*d
|
| | |
|
|\ \
| |/
|/| |
DOC: #7927. Remove deprecated note for memmap relevant for Python <2.5
|
| | |
|
| | |
|
|/ |
|
|\
| |
| | |
BUG: Guard against buggy comparisons in generic quicksort.
|