| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
(The existing example already showcases the contracted axis stacking.)
|
|
|
| |
Axes shift description and example of np.tensordot in its doc string
|
|
|
|
|
|
|
| |
Alter test to check if arrays are the same to avoid in-place of some
array-like objects
closes #11975
|
|\
| |
| | |
ENH: check getfield arguments to prevent invalid memory access
|
| | |
|
| |
| |
| |
| |
| | |
* add additional test cases for test_issctype
requested by @eric-wieser in gh-12109
|
|\ \
| | |
| | | |
MAINT: Ensure that a copy of the array is returned when calling `block`.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In the case that a user calls
np.block(array),
the old block function would return a view into the array.
This ensures that a new array is returned
|
|\ \ \
| | | |
| | | | |
BUG: limit default for get_num_build_jobs() to 8
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The default value for get_num_build_jobs() is now the number of CPUs
limited to a maximum of 8. This is to prevent overloading systems
with a lot of CPUs. See ticket #12087
|
|\ \ \ \
| | | | |
| | | | | |
TST: add unit test for issctype
|
| | |_|/
| |/| | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* Validate dispatcher functions in array_function_dispatch
They should have the same signature as the decorated function.
Note: eventually these checks should be optional -- we really only need them
to be run as part of NumPy's test suite, not every time numpy is imported.
* ENH: make signature checking in array_function_dispatch optional
* Change verify_signature keyword argument to verify
|
|\ \ \ \
| |/ / /
|/| | | |
MNT Update pickling test by making them loop over all protocols
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |/ / |
|
|\ \ \
| | | |
| | | | |
TST, MAINT: Skip some f2py tests on Mac.
|
| |/ /
| | |
| | |
| | |
| | |
| | | |
There is a not yet understood problem in testing f2py C modules (*.pyf)
files on the Mac that manifests as erratic module import failures.'
This disables those tests until we can figure out what the problem is.
|
|\ \ \
| | | |
| | | | |
ENH: Extend info in Invalid integer dtype error message
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Otherwise it is hard to impossible to figure out what is the actual
value which fails the test.
See e.g. failing on 3.4 (only) tests of nibabel:
https://ci.appveyor.com/project/nipy/nibabel/build/1.0.498/job/eechfm1kxroa0rju#L598
|
|/ / |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Extend the blacklist to MSVC 2017 and add functions
- CSQRT
- CSQRTF
- CSQRTL
- CLOG
- CLOGF
- CLOGL
- CACOS
- CACOSF
- CACOSL
- CACOSH
- CACOSHF
- CACOSHL
See comment from cgholke at issue #11855.
|
|\ \
| | |
| | | |
ENH: Chain exceptions to give better error messages for invalid PEP3118 format strings
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
format strings
Sample console output:
```
In [1]: from ctypes import c_wchar
In [2]: x = c_wchar * 3
In [3]: np.array(x())
---------------------------------------------------------------------------
ValueError Traceback (most recent call last)
~\Repos\numeric-python\numpy\build\testenv\Lib\site-packages\numpy\core\_internal.py in _dtype_from_pep3118(spec)
486
--> 487 dtype, align = __dtype_from_pep3118(stream, is_subdtype=False)
488 return dtype
~\Repos\numeric-python\numpy\build\testenv\Lib\site-packages\numpy\core\_internal.py in __dtype_from_pep3118(stream, is_subdtype)
558 else:
--> 559 raise ValueError("Unknown PEP 3118 data type specifier %r" % stream.s)
560
ValueError: Unknown PEP 3118 data type specifier 'u'
The above exception was the direct cause of the following exception:
ValueError Traceback (most recent call last)
<ipython-input-3-f8a17df3aa24> in <module>()
----> 1 np.array(x())
ValueError: '<u' is not a valid PEP 3118 buffer format string
```
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* test_path() in test_memmap.py no longer
uses os.path.realpath() because of failure
to resolve symlinks on Windows--a CPython
bug that is still open
* this was discovered in testing on the Azure
CI platform, where a symlink was resolved
by memmap in NumPy using Path.resolve(), while
the unit test verifying this behavior used
os.path.realpath()
|
|\ \ \
| | | |
| | | | |
MAINT: speed up _block by avoiding a recursive closure
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Fixes #11993
|
|\ \ \ \
| | | | |
| | | | | |
MAINT: remove redundant imports
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
MAINT: remove unused stdlib imports
|
| |/ / / / |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
MAINT: remove redundant assignment
|
| |/ / / / |
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
BUG: define "uint-alignment", fixes complex64 alignment
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
Implements IsAligned, IsUintAligned, npy_uint_alignment
|
| | | | | |
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
ENH: maximum lines of content to be read from numpy.loadtxt
|