| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes GH3290
With apologies to mwiebe, this rips out most of the time zone parsing from
the datetime64 type.
I think we mostly sorted out the API design in discussions last year, but
I'll be posting this to the mailing list shortly to get feedback.
Old behavior:
# string parsing and printing defaults to your local timezone :(
>>> np.datetime64('2000-01-01T00')
numpy.datetime64('2000-01-01T00:00-0800','h')
New behavior:
# datetime64 is parsed and printed as timezone naive
>>> np.datetime64('2000-01-01T00')
numpy.datetime64('2000-01-01T00','h')
# you can still supply a timezone, but you get a deprecation warning
>>> np.datetime64('2000-01-01T00Z')
DeprecationWarning: parsing timezone aware datetimes is deprecated; this
will raise an error in the future
numpy.datetime64('2000-01-01T00','h')
|
| |
|
|\
| |
| | |
BUG: Enforce Order Param for MaskedArray Construction
|
| |
| |
| |
| |
| |
| |
| |
| | |
Adds the 'order' parameter to the __new__ override
in MaskedArray construction, enabling it to be enforced
in methods like np.ma.core.array and np.ma.core.asarray.
Closes gh-6646.
|
|\ \
| |/
|/| |
DOC: Clean up/fix several references to the "future" 1.10 release
|
| |
| |
| |
| | |
Fixes gh-7010
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Now, NaT compares like NaN:
- NaT != NaT -> True
- NaT == NaT (and all other comparisons) -> False
We discussed this on the mailing list back in October:
https://mail.scipy.org/pipermail/numpy-discussion/2015-October/073968.html
|
|\ \
| | |
| | | |
BUG: fix casting rules for generic datetime64/timedelta64 dtypes
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fixes GH6452
There are two types of datetime64/timedelta64 objects with generic times
units:
* NaT
* unit-less timedelta64 objects
Both of these should be safely castable to any more specific dtype. However,
more specific dtypes should not be safely castable to generic units.
Otherwise, the result of `np.datetime64('NaT')` or `np.timedelta(1)` is
entirely useless, because they can't be used in any arithmetic operations or
comparisons.
This is a regression from NumPy 1.9, where these sort of operations worked
because the default casting rules with ufuncs were less strict.
|
| | |
| | |
| | |
| | |
| | |
| | | |
I have found that there are two missing numbers in a sequence in the documentation.
http://docs.scipy.org/doc/numpy/user/misc.html#interfacing-to-c
It goes 1,2,3,5,7,8 with missing 4 and 6.
|
| | |
| | |
| | |
| | |
| | | |
empty strings are the default for the new rpath,
extra_compile_args and extra_link_args sections
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
gerritholl/structured_multidim_masked_array_fillvalue
BUG/TST: Fix for #6723 including test: force fill_value.ndim==0
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Fix issue #6723. Given an exotic masked structured array, where one of
the fields has a multidimensional dtype, make sure that, when accessing
this field, the fill_value still makes sense. As it stands prior to this
commit, the fill_value will end up being multidimensional, possibly with
a shape incompatible with the mother array, which leads to broadcasting
errors in methods such as .filled(). This commit uses the first element
of this multidimensional fill value as the new fill value. When more
than one unique value existed in fill_value, a warning is issued.
Also add a test to verify that fill_value.ndim remains 0 after indexing.
|
|\ \ \ \
| | | | |
| | | | | |
BUG: Add more complex trig functions to glibc < 2.16 blacklist.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Added functions are
- cacos
- cacosf
- cacosl
- cacosh
- cacoshf
- cacoshl
Closes #6063.
|
| | | | |
| | | | |
| | | | |
| | | | | |
and calls `PyArray_MatrixProduct2`.
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
`PyObject_Repr`. Also, do a better job of handling any errors raised while constructing the error message.
|
| | | | |
| | | | |
| | | | |
| | | | | |
common type.
|
| |_|_|/
|/| | |
| | | |
| | | | |
common type.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
may return something else than one or zero and npy_bool is
unfortunately an int8 not a c99 bool
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
ENH: vectorize isinf and isfinite
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
isfinite is especially valuable as its needed to verify inputs are
suitable for lapack.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
ENH: moveaxis function
|
| | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Fixes GH2039
This function provides a much more intuitive interface than `np.rollaxis`,
which has a confusing behavior with the position of the `start` argument:
http://stackoverflow.com/questions/29891583/reason-why-numpy-rollaxis-is-so-confusing
It was independently suggested several times over the years after discussions
on the mailing list and GitHub (GH2039), but never made it into a pull request:
https://mail.scipy.org/pipermail/numpy-discussion/2010-September/052882.html
My version adds support for a sequence of axis arguments. I find this behavior
to be very useful. It is often more intuitive than supplying a list of
arguments to `transpose` and also nicely generalizes NumPy's existing axis
manipulation routines, e.g.,
def transpose(a, order=None):
if order is None:
order = reversed(range(a.ndim))
return moveaxes(a, order, range(a.ndim))
def swapaxes(a, axis1, axis2):
return moveaxes(a, [axis1, axis2], [axis2, axis1])
def rollaxis(a, axis, start=0):
if axis < start:
start -= 1
return moveaxes(a, axis, start)
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
form.
|
| | | | |
| | | | |
| | | | |
| | | | | |
products. Add some tests for matrix products. Include a `syrk` vs. `gemm` test case.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
MAINT, STY: Removed unused variable in f2py/f90mod_rules.py
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
DOC: Update 6972
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
[ci skip]
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
[ci skip]
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
[ci skip]
|
|/ / / / / /
| | | | | |
| | | | | |
| | | | | | |
[ci skip]
|
|\ \ \ \ \ \
| |_|_|/ / /
|/| | | | | |
BLD: fix build error for mingw32 compiler on Windows
|
| | | | | |
| | | | | |
| | | | | | |
Related Issue http://stackoverflow.com/questions/33886558/numpy-installation-error-mingw32ccompiler-instance-has-no-attribute-compile-o
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
STY: Place conditional opening braces on the same line
|
| | |/ / /
| |/| | | |
|
|/ / / /
| | | |
| | | |
| | | | |
Fixes gh-6712.
|
|\ \ \ \
| |/ / /
|/| | | |
MAINT: distutils cleanup for Pyrex support and unused f2py/swig tests
|
| | | | |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
ENH: Use `syrk` to compute certain dot products more quickly and accurately
|
| | | | |
| | | | |
| | | | |
| | | | | |
accurately in certain special cases.
|
| | | | | |
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
ENH: allow single input argument in numpy.broadcast
|
| | | | | |
|
| | | | | |
|