| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
``np.npv`` calculates the present value of a series of cashflows
starting in the present (t=0). Another common definition of NPV
uses the future cashflows i.e. starting at the end of the first
period.
The difference in definition can lead to confusion for users moving
between NumPy and other projects [1] and adds complexity for
maintainers [2]. This commit adds a warning to the ``npv``
function's documentation and adds an example on how to find the npv
of a project using the alternate definition.
[1] https://github.com/numpy/numpy/issue/10877
[2] https://github.com/numpy/numpy/pull/3346
|
| |\ \
| | |
| | | |
BUG: fix inconsistent axes ordering for axis in function `unique`
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
BUG: Fix uint-overflow if padding with linear_ramp and negative gain
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
linspace supports non-scalar values since version 1.16. This can replace
the former _linear_ramp method.
This removes a bug in the old implementation where certain edge and
end values resulted in an integer underflow for unsigned dtypes (see
gh-14191). Protect against this regression with a new test for all
numeric dtypes.
|
| |\ \ \ \
| | | | |
| | | | | |
DOC: lib: Add more explanation of the weighted average calculation.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Also removed the incorrect comment from the docstring of `numpy.ma.average`
about the imaginary part of `weights` being ignored.
|
| |\ \ \ \ \
| |/ / / /
|/| | | | |
DOC: Fixed dtype docs for var, nanvar.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Docs incorrectly stated that the default output dtype was float32 when
input array is of an integer dtype. However:
```python
np.var(np.random.randint(0, 100, 1000)).dtype == np.dtype("f8")
```
|
| | | | | |
| | | | |
| | | | |
| | | | | |
* Deprecate class SafeEval
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
MAINT: Fix behavior of structured_to_unstructured on non-trivial dtypes
|
| | | |_|_|/
| |/| | |
| | | | |
| | | | | |
Fixes #13333
|
| |\ \ \ \ \
| |/ / / / |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
(#14070)
* DOC:Add example to clarify "numpy.save" behavior on already unclosed file
|
| | |\ \ \ \
| | | | | |
| | | | | | |
MAINT: Clearer error message while padding with stat_length=0
|
| | | | |/ /
| | |/| |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Provides a clearer error message if stat_length=0 is the cause of an
exception (mean and median return nan with warnings) as well as tests
covering this behavior.
Note: This shouldn't change the behavior/API except for the content of
the raised ValueError.
|
| | | |_|/
| |/| | |
|
| | |/ /
| | |
| | | |
* DOC: new nan_to_num keywords are from 1.17 onwards
|
| | | | |
|
| | | | |
|
| | |\ \
| | | |
| | | | |
BUG: Fix file-like object check when saving arrays
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
For writing arrays, only the ``write`` method is necessary.
|
| | |\ \ \
| | |/ /
| |/| | |
BUG, DOC: add new recfunctions to `__all__`
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When a buffer interface does not request a writeable buffer,
simply pass a read-only one when the warn on write flag is set.
This is to give an easier way forward with avoiding the deprecation
warnings: Simply do not ask for a writeable buffer.
It will break code that expects writeable buffers but does not
ask for them specifically a bit harder than would be nice.
But since such code probably should ask for it specifically, this
is likely fine (an RC release has to find out).
The main reason for this is, that this way it plays very will with
cython, which requests writeable buffers explicitly and if declared
`const` is happy about read-only (so that using `const` is the best
way to avoid the warning and makes code cleaner).
Closes gh-13929, gh-13974
|
| | |/ /
| | |
| | | |
I think it should be like that (maybe I am mistaken).
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
For array likes supporting UFuncs, `np.abs` would return an array-like,
and this is currently not compatible with the use of `np.piecewise`.
The simplest fix seems to be to just call asanyarray (which piecewise
calls anyway on the array) beforehand. This way we ensure the conditions
are also an array.
Fixes gh-13894
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* BUG: Fix leaking of object descriptor on dtype discovery of `None`
* BUG: Fix reference count leak in string discovery code path
* BUG: Fix two more datetime related reference count bugs
One is leaking only the python integer 1, the other a descriptor.
* BUG: Fix bugs in vectorized string functions error paths
Fixes reference count issues (a leak) in
TestVecString::test_non_existent_method and
TestVecString::test_non_string_array
* BUG: Fix Reference count leak in in128 C-level tests
* BUG: Fix refcount leak in advanced indexing error path
* BUG,MAINT: Refactor indexing dtypes handling in mapiter constructor
Using borrowed references for the dtypes seems much easier to get
the reference counts right.
* BUG: Reference leaks in deprecated datetime with timezone coercion
* BUG: Refcount issue in nonzero 0-d path
* BUG: Fix ufunc.at dtype refcount handling in resolver
* BUG: Fix reference count in nditer python op_axes setup
* BUG: Reference leak in writebackifcopy non-array error path
* BUG: Add missing DECREF in ufunc with dtype type resolution
* BUG: Reference count bugs in io functions
* BUG: Reference count loss in as_c_array C-side tests
* BUG: Leaking of method in object method based ufunc loops
The function could possibly be optimized nicely by checking
that the method will be the same because the types are identical.
OTOH, that may not be correct in dynamically adapted types.
* TST: Clean up cyclic ctypes reference to simplify leak debugging
If we do not clean it up in this test, the collection can take
so long that it affects the following tests when running with
reference leak debugging tools (pytest-leaks).
* BUG: Reference count of raw data for 0-sized unpickling
* TST: Mark tests which must leak references
It really may be time to remove this, considering how annoying this
is, may want to think about getting rid of that behaviour.
Could probably write a multiearraytests C-side function instead.
* BUG: Fix refcount leaks in arr.getield and setfield error paths
* BUG: Fix refcount issue in wheremask
This fix is not the prettiest, since it relies on the wheremask
to be formatted to boolean beforehand correctly.
* TST: Reset StringConvert after mutating it in tests
Or maybe just mark the test?
* BUG: Fix missing static for npy_cache_import in umath funcs.inc.src
* BUG: Fix refcount in multiternew error path
* BUG: Fix npy_ObjectGCD and LCM reference counting
* BUG: Decrement already wrapped outputs on failure
This is not super pretty, but not sure how to do it much better
right now.
* FIXUP: iotools StringConverter._mapper
* FIXUP: as_c_array tests
* FIXUP: String/dtype discovery comment
* FIXUP: Nonzero comment
* FIXUP: mapiternew -- check error return of dtype creation
In principle, at least at this time, this is not possible
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When the base is not an array (or generally when the flag of the base
array was toggled), it is OK to allow setting the writeable flag to
True, as long as any ancestor (especially the last one) is writeable.
This commit also slightly change the behaviour of the base attribute.
---
* ENH: Deprecate writeable broadcast_array
* ENH: Make writeable flag enabling more reliable for non-array bases
When the base is not an array (or generally when the flag of the base
array was toggled), it is OK to allow setting the writeable flag to
True, as long as any ancestor (especially the last one) is writeable.
* Update doc/release/1.17.0-notes.rst
Co-Authored-By: Sebastian Berg <sebastian@sipsolutions.net>
* Update doc/release/1.17.0-notes.rst
Co-Authored-By: Sebastian Berg <sebastian@sipsolutions.net>
* Update numpy/lib/tests/test_stride_tricks.py
Co-Authored-By: Sebastian Berg <sebastian@sipsolutions.net>
* Update numpy/core/tests/test_multiarray.py
Co-Authored-By: Sebastian Berg <sebastian@sipsolutions.net>
* DOC: improve warning (from review)
|
| | |\ \ |
|
| | | |/
| | |
| | |
| | | |
Now with tests....
|
| | | | |
|
| | | | |
|
| | | |\
| | | |
| | | | |
MAINT: fix histogram*d dispatchers
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
fixes GH-13728
|
| | | |/ |
|
| | | |\
| | | |
| | | | |
DOC: Document/ Deprecate functions exposed in "numpy" namespace
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
