| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
* C source comments flag two extraneous checks for
the object type of self->subarray->shape in
descriptor.c
* pertinent code has been adjusted to assert
the presence of the tuple object where
needed & remove a fallback return call along
with an extraneous casting
|
|
|
|
|
|
|
|
|
|
|
|
| |
* fixed doc typo
* fixed lib typos
* fixed lapack_lite typos
* Revert "fixed lapack_lite typos"
This reverts commit e7dada860cb73af190234402508ab79965ecd079.
|
|\
| |
| | |
BUG: it.close() disallows access to iterator, fixes #10950
|
| | |
|
| | |
|
| | |
|
|\ \
| |/
|/| |
TST: Extract a helper function to test for reference cycles
|
| |
| |
| |
| | |
It's not always possible to guarantee this, so also adds a test to verify that we don't hang
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
An example output for the test added in the previous commit is:
AssertionError: Reference cycles were found when calling make_cycle: 1 objects were collected, of which 1 are shown below:
list object with id=2279664872136:
[<Recursion on list with id=2279664872136>,
<Recursion on list with id=2279664872136>]
|
| |
| |
| |
| |
| |
| | |
This also means we can now test that our test is actually able to detect the type of failure we expect
Trying to give myself some tools to debug the failure at https://github.com/numpy/numpy/pull/10882/files#r180813166
|
|\ \
| | |
| | | |
ENH: Nditer as context manager
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Some links in developer documentation and files had extraneous '-dev' in
them, removing it restore the working state of the links.
See: #10939
|
|\ \ \
| | | |
| | | | |
DOC: clear up warnings, fix matplotlib plot
|
| | | | |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
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.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
DOC: Fix NumpyVersion example (closes gh-10935)
|
| | | | | | |
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
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.
|
|\ \ \ \ \ \
| |_|_|_|/ /
|/| | | | | |
Fixes #663: fixed dtype alignment for array of structs in case of converting from tuple descr
|
| | |_|/ /
| |/| | |
| | | | |
| | | | | |
from tuple descr
|
|/ / / /
| | | |
| | | |
| | | | |
Closes #10847
|
| | | |
| | | |
| | | |
| | | | |
Fixes gh-10780
|
|\ \ \ \
| | | | |
| | | | | |
Add missing underscore to prototype in check_embedded_lapack
|
| | | | | |
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
DOC: rework documents and silence warnings during sphinx build
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
BUG: fix savetxt, loadtxt for '+-' in complex
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
TST: reactivate module docstring tests, fix float formatting
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| |/ / / / / /
|/| | | | | | |
DOC: Fix link in `See Also` section of `randn` docstring.
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
DOC: Cross-reference full/full_like in a few "See Also" sections.
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
While teaching numpy I was asked the best way to create an array of nan,
and `np.full` seem not be cross linked from many places; In particular
in the documentation of `zeros` and `ones` seam like obvious candidates
to add them.
Reorder all the see-also to be
- empty_like
- ones_like
- zero_like
- full_like
- empty
- ones
- zeros
- full
|
| |/ / / / / /
|/| | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
* fixes #10886 : Bad link to `np.random.randint`
* Issue #10886: Change from `np.random.randint` to `randint` in 'See Also` doc-string section of mtrand.pyx
|
|\ \ \ \ \ \ \
| |_|_|_|_|_|/
|/| | | | | | |
ENH: umath: don't make temporary copies for in-place accumulation
|
| | |/ / / /
| |/| | | |
| | | | | |
| | | | | | |
Do the operation `ufunc.accumulate(x, out=x)` without temporary copies.
|