| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
MAINT: One step closer to vectorizing lstsq
|
| | |
|
| |
| |
| |
| | |
not the first
|
| | |
|
| |
| |
| |
| |
| | |
Add regression test that checks for certain bugs where results from sdot
change if certain libraries are imported first.
|
|\ \ |
|
| |\ \
| | | |
| | | | |
MAINT: move linalg tests using matrix to matrixlib
|
| | | |
| | | |
| | | |
| | | |
| | | | |
This is in preparation for deprecation and eventual removal
of the matrix class.
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* BUG: optimizing compilers can reorder call to npy_get_floatstatus
* alternative fix for npy_get_floatstatus, npy_clear_floatstatus
* unify test with pr #11043
* use barrier form of functions in place of PyUFunc_{get,clear}fperr
* update doc, prevent segfault
* MAINT: Do some rewrite on the 1.15.0 release notes.
[ci skip]
|
| | |
| | |
| | |
| | |
| | | |
Since linalg allows stacks of matrices generally, there is no
reason not to allow it for matrix_power.
|
|/ /
| |
| |
| |
| | |
The docstring already assumed it was in linalg, and this ensures
linalg becomes completely independent of matrixlib.
|
|\ \
| |/
| | |
MAINT: lstsq: compute residuals inside the ufunc
|
| |
| |
| |
| |
| |
| | |
This prevents an overly large output array being allocated.
It also means the the residuals can be handled as a separate out argument in future.
|
|\ \
| | |
| | | |
BUG: Return NULL from PyInit_* when exception is raised
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
I don't think this is documented anywhere, but I'm pretty sure module init
functions should return NULL in order to communicate that an exception
occurred during initialization (as is the standard Python/C API convention).
It's clear from the CPython code
[here](https://github.com/python/cpython/blob/master/Python/importdl.c#L162)
that if you don't return NULL, the exception is swallowed and replaced with the
message "initialization of %s raised unreported exception".
Admittedly, this is only useful for people porting Numpy to new platforms where
it is helpful to know where module initialization is failing, but it can't hurt.
|
|\ \ \
| |_|/
|/| | |
DOC: rework documents and silence warnings during sphinx build
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
This does not yet enable any broadcasting, but makes doing so in future far
easier.
|
| | | |
|
| | | |
|
|/ / |
|
| |
| |
| |
| |
| | |
That function is nose specific and has not worked since `__init__` files
were added to the tests directories.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Numpy can now be tested using the standard
`python -c"import numpy; numpy.test()"`
construct.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Use standard pytest markers everywhere in the numpy tests. At this point
there should be no nose dependency. However, nose is required to test
the legacy decorators if so desired.
At this point, numpy test cannot be run in the way with runtests, rather
installed numpy can be tested with `pytest --pyargs numpy` as long as
that is not run from the repo. Run it from the tools directory or some
such.
|
|/
|
|
|
| |
The "bench" testing with the old bench files is no longer supported.
These days we use `runtests.py` and `asv`.
|
|
|
|
|
|
|
|
|
|
| |
* MAINT: Replace print statements for Python3.
Updates tools/swig/test/testSuperTensor.py.
* MAINT: Fix deprecated escaped characters for python 3.6+.
Update numpy/linalg/lapack_lite/clapack_scrub.py.
|
|\
| |
| | |
BLD: Add configuration changes to allow cross platform builds for iOS.
|
| |
| |
| |
| |
| |
| |
| |
| | |
When building NumPy for iOS, you build on macOS, with compiler flags to target iOS or the iOS simulator. However, setup.py runs on macOS, so sys.platform == 'darwin', regardless of the platform being targetted.
distutils provides an environment variable - _PYTHON_HOST_PLATFORM - to indicate when you are building for a different platform. This patches uses that variable to identify cross-platform builds and disable macOS specific features.
The patch also renames an internal method in strfuncs to avoid a collision with a symbol in iOS's standard library, and includes math.h to avoid errors about undefined symbols.
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Align type definitions
* Regenerate sources
* Replace BytesIO
* Consolidate executables
* Create directories on PY2
* Revise step name
* Consolidate directory creation
* Don't catch makedirs errors
* Revise step name
* Add header source
|
|
|
| |
[ci skip]
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Make np.linalg.cond(A, p) always use SVD for p=+-2 and not only p=None.
Ensure inf is returned instead of nan when the condition number diverges
for +/-2 norm.
Ignore errors when inverting matrices for p = +-1, 'fro', +-inf, so that
spurious LinAlgErrors are not raised. In those cases, report
non-invertible matrices as having cond=inf.
Add additional tests for cond().
|
| |
|
| |
|
|\
| |
| | |
MAINT: Fix sign-compare warnings in umath_linalg.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The sign-compare warning is enabled for python 3.5+ builds and
the warnings have been causing wheel build failures on travis ci.
The replacements here of `size_t` and `ptrdiff_t` by `npy_intp` should
be safe given that the sizes of numpy arrays in bytes are specified by
those types. A bigger problem is that most BLAS libraries are compiled
with smaller integer types. I don't know where that is checked, or even
if it is checked.
|
|/
|
|
|
| |
Fixes #5727
The axis argument was introduced in #3387
|
|\
| |
| | |
MAINT: Adjust type promotion in linalg.norm
|
| |
| |
| |
| | |
Fixes gh-10364, partly by adjusting the promise in the release notes
|
| | |
|
| | |
|
|/ |
|
|
|
|
|
| |
This takes care of the licenses for the libraries included in the NumPy
repository or bundled in the NumPy source distributions.
|
|
|
|
| |
F2C does not support complex return values.
|
| |
|
|
|
|
| |
This takes gh-5909 a little further.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This fixes a bug in the creation of workspace arrays for a call
to `lapack_lite.zgelsd`, which led to segmentation faults when
a RHS was passed in that had larger size than the size of the
matrix.
|