| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The 2001 date I had originally was based on the beginning of NumPy's git
history -- but further research suggests that this actually runs back
into Numeric times, before the NumPy project was founded.
New 2005 date is based on Fernando's recollection of the fateful meeting
that led to NumPy's creation, and is consistent with Wikipedia's claim
that 2006 was the first release.
If this is wrong please let me know :-)
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
I used pandoc to convert Markdown to ReST, and for some reason it marked
all the links with two underscores instead of the more conventional
single underscore. I'm not sure why.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
See Travis's email here:
https://mail.scipy.org/pipermail/numpy-discussion/2015-September/073712.html
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The NumFOCUS subcommittee and Institutional Partners are now listed in a
separate file, so delete them from here.
We will eventually want to clean up the list of initial members of the
steering council, but the details are still under discussion on the
mailing list, so I left that section alone for now.
|
| |/
| |
| |
| |
| |
| |
| | |
This is definitely *not* the final version -- it's the version
originally posted to the mailing list, reformatted as ReST. I'll make
further changes on top of this as further commits, in order to preserve
the historical record.
|
|/
|
|
|
|
|
|
| |
The check_return argument and ufunc object field was never used; ditto
for the "new" inner loop selector (which was never implemented), along
with associated typedefs. Since I was looking at this code anyway trying
to figure out which parts were actually in use, I figured I'd clear up
some of the brush to make it easier next time...
|
| |
|
|
|
|
|
| |
Bento builds are no longer supported, so remove references to that
built system.
|
| |
|
|
|
|
|
| |
It may be that you can say that it cannot happen when grow inner
is not enabled as well.
|
|
|
|
| |
[ci skip]
|
| |
|
|
|
|
| |
The lists needed blank lines before starting.
|
|
|
|
| |
The proper reference is in routines.rst.
|
|
|
|
| |
Also correct its documented default value.
|
|
|
|
| |
List needs to be preceded by blank line.
|
| |
|
|
|
|
|
|
|
| |
Examples
:cdata: -> :c:data:
.. cfunction:: -> .. c:function::
|
|
|
|
|
|
|
| |
Update docs for boolean array indexing and nonzero order.
Add links to row-major and column-major terms where they appear.
Closes #3177
|
|
|
|
|
|
|
|
|
|
|
|
| |
Viewing an ndarray as a np.recarray now automatically converts
the dtype to np.record.
This commit also fixes assignment to MaskedArray's dtype attribute,
fixes the repr of recarrays with non-structured dtype, and removes
recarray.view so that viewing a recarray as a non-structured dtype
no longer converts to ndarray type.
Fixes #3581
|
| |
|
|
|
|
|
| |
Document the matmul function and add '@' to the operator
section of the reference manual.
|
|\
| |
| | |
New typemap for in-place arrays of arbitrary number of dimensions:
|
| |
| |
| |
| |
| | |
(DATA_TYPE* INPLACE_ARRAY_FLAT, DIM_TYPE DIM_FLAT)
Added unittests, updated documentation.
|
| | |
|
|\ \
| |/
|/| |
DOC: Commit message lines should not excede 72 characters.
|
| |
| |
| |
| |
| | |
The reason is that git log indents parts of the message and longer
lines will wrap. Linus has a post on this somewhere.
|
|\ \
| | |
| | | |
ENH: add np.stack
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The motivation here is to present a uniform and N-dimensional interface for
joining arrays along a new axis, similarly to how `concatenate` provides a
uniform and N-dimensional interface for joining arrays along an existing axis.
Background
~~~~~~~~~~
Currently, users can choose between `hstack`, `vstack`, `column_stack` and
`dstack`, but none of these functions handle N-dimensional input. In my
opinion, it's also difficult to keep track of the differences between these
methods and to predict how they will handle input with different
dimensions.
In the past, my preferred approach has been to either construct the result
array explicitly and use indexing for assignment, to or use `np.array` to
stack along the first dimension and then use `transpose` (or a similar method)
to reorder dimensions if necessary. This is pretty awkward.
I brought this proposal up a few weeks on the numpy-discussion list:
http://mail.scipy.org/pipermail/numpy-discussion/2015-February/072199.html
I also received positive feedback on Twitter:
https://twitter.com/shoyer/status/565937244599377920
Implementation notes
~~~~~~~~~~~~~~~~~~~~
The one line summaries for `concatenate` and `stack` have been (re)written to
mirror each other, and to make clear that the distinction between these functions
is whether they join over an existing or new axis.
In general, I've tweaked the documentation and docstrings with an eye toward
pointing users to `concatenate`/`stack`/`split` as a fundamental set of basic
array manipulation routines, and away from
`array_split`/`{h,v,d}split`/`{h,v,d,column_}stack`
I put this implementation in `numpy.core.shape_base` alongside `hstack`/`vstack`,
but it appears that there is also a `numpy.lib.shape_base` module that contains
another larger set of functions, including `dstack`. I'm not really sure where
this belongs (or if it even matters).
Finally, it might be a good idea to write a masked array version of `stack`.
But I don't use masked arrays, so I'm not well motivated to do that.
|
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Basic cleanup of the new indexing documentation. Also replace
"subspace" by "subarray" and try to clarify mixed advanced and view
indexing.
[skip ci]
|
| | |
|
| |
| |
| |
| |
| |
| | |
Closes gh-5684.
[ci skip]
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Raises a TypeError if any of the keyword arguments supplied to a
ufunc does not exactly match the name in the signature. Prior to
this, trailing characters were discarded, e.g. 'out2' would be
treated as if it where 'out'.
|
|\ \
| | |
| | | |
ENH: ufuncs can take a tuple of arrays as 'out' kwarg
|
| | |
| | |
| | |
| | | |
Closes #4752
|
|/ /
| |
| |
| |
| |
| | |
Version information added in the Notes section of the functions
accepting stacked arrays and in the discussion of this feature
in the linalg overview.
|
|/
|
|
|
|
|
|
| |
Per the mailing list discussion [1], I have implemented a new function
`broadcast_to` that broadcasts an array to a given shape according to
numpy's broadcasting rules.
[1] http://mail.scipy.org/pipermail/numpy-discussion/2014-December/071796.html
|
|\
| |
| | |
genfromtxt example in user docs missing delimiter
|
| |
| |
| | |
The example given in the user docs does not run correctly without adding `delimiter=","`. This add the missing keyword to allow the examples to be run.
|
|/
|
|
|
|
|
| |
SWIG interface has moved to tools/ directory, so updating the doc to state that
and also the number of tests is reduced since what reported, so a generic "more
than" is used (to avoid similar situations in the future) but likely also the
other numbers should be checked.
|
| |
|
| |
|
|\
| |
| | |
DOC: add documentation for some scalar checks
|
| |
| |
| |
| | |
DOC: Mention that PyArray_Return steals a reference to arr
|
|\ \
| | |
| | | |
DOC: update build instructions, add developer docs
|
| | |
| | |
| | |
| | |
| | |
| | | |
Addresses review comments on gh-5473.
[ci skip]
|