| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
| |
[ci skip]
|
| |
|
|
|
|
|
| |
* Drop testing of Python 2.6, 3.2, and 3.3
* Create 1.12.0-notes.rst and add to source/documentation.
* Update pavement.py to use 1.10.x as LOG_START
* Update version numpy in setup.py
|
| |
|
|
|
|
| |
Rewrite the documentation of added functionality of the deg parameter of
the polynomial fitting functions in the numpy.polynomial package and put
it in the 'New Features' section.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Only for 1d-ndarrays exactly, as subtypes (e.g. masked arrays) may not
allow direct shuffle of the underlying buffer (in fact, the old
implementation destroyed the underlying values of masked arrays while
shuffling).
Also handles struct-containing-object 1d ndarrays properly.
See #6776 for an earlier, less general (but even faster: ~6x)
improvement attempt, #5514 for the original issue.
|
| |\
| |
| | |
API: Make datetime64 timezone naive
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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')
|
| |\ \
| | |
| | | |
BLD: fix runtests.py, was broken by the move to setuptools.
|
| | | |
| | |
| | |
| | | |
[ci skip]
|
| |/ / |
|
| | |
| |
| |
| | |
been extended to several NumPy operations.
|
| |\ \
| | |
| | | |
BLD: build improvements (enable setuptools)
|
| | | |
| | |
| | |
| | | |
Address comments of @charris on gh-6895.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Also remove all mentions of setupegg.py from the documentation.
|
| |\ \ \
| |/ /
|/| | |
DEP: Warn MaskedArray will return views of mask when sliced
|
| | |/
| |
| |
| | |
their masks when they are also returning views of their data.
|
| |\ \
| | |
| | | |
DOC: Release 1.11.0 text `code` -> ``code``
|
| | |/ |
|
| |/
|
|
| |
cast to a common type.
|
| |\
| |
| | |
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.
|
| |/
|
|
| |
Fixes gh-7010
|
| | |
|
| |\
| |
| | |
STY, DOC: Fix indentation and typos in example
|
| | | |
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
| |\
| |
| | |
MAINT: distutils cleanup for Pyrex support and unused f2py/swig tests
|
| | |
| |
| |
| | |
[ci skip]
|
| |\ \
| | |
| | | |
DOC: Sync 1.10.3 and 1.10.4 release notes, update reference doc.
|
| | | | |
|
| |\ \ \
| |/ /
|/| | |
ENH: Use `syrk` to compute certain dot products more quickly and accurately
|
| | |/
| |
| |
| | |
and `A @ A.T`.
|
| | | |
|
| |\ \
| | |
| | | |
ENH: allow single input argument in numpy.broadcast
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
DOC: update 1.10.3 release notes.
|
| | | |/
| |/|
| | |
| | | |
[ci skip]
|
| |/ /
| |
| |
| | |
[skip ci]
|
| | |
| |
| |
| | |
[skip ci]
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Some of the documentation for newbyteorder, copy and pasted in several
spots, had paragraphs ending in `::`, initiating a sphinx generated
Verbatim environment and resulting in "LaTeX Error: Too deeply nested".
The user_array.container class needed non-empty class documentation.
That that caused a problem is probably a numpydoc bug, but it is easy to
fix.
[skip ci]
|
| | | |
|
| |/ |
|
| | |
|
| |\
| |
| | |
ENH: Add dtype argument to random.randint.
|
