summaryrefslogtreecommitdiff
path: root/doc/source/reference
Commit message (Collapse)AuthorAgeFilesLines
* MAINT: Fix typos in docsDongjoon Hyun2016-01-256-6/+6
|
* Merge pull request #6453 from shoyer/naive-datetime64Charles Harris2016-01-161-25/+37
|\ | | | | API: Make datetime64 timezone naive
| * API: Make datetime64 timezone naiveStephan Hoyer2016-01-151-25/+37
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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')
* | DOC: add NumpyVersion to the docs, and mention it in version.pyRalf Gommers2016-01-161-0/+7
|/
* DOC: Clean up/fix several references to the "future" 1.10 releaseNathaniel J. Smith2016-01-141-2/+2
| | | | Fixes gh-7010
* ENH: moveaxis functionStephan Hoyer2016-01-091-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* Fix carriage return inside commented python codeVincent Legoll2015-12-261-2/+2
| | | This looks more conventionnal
* DOC: fix method signatures in "array subclasses"Matthias Geier2015-12-111-6/+6
| | | | | | * Change ".. function::" -> ".. method::" * Remove "self" argument * Change "self" to "obj" in __array_finalize__
* MAINT: Typo in arrays.indexing.rst Issue#6670floatingpointstack2015-11-121-1/+1
|
* DOC: reorganize user guide a bit + import "tentative numpy tutorial" from wikiPauli Virtanen2015-10-251-0/+2
| | | | | | | | The user guide was missing a quick tutorial --- the basics.* stuff is somewhat too complex already. The "building numpy" instructions also should not be "introductory material".
* DOC: typo in arrays.interface.rst #6516Alain2015-10-201-1/+1
|
* DOC: fixed #6525Yifan Li2015-10-191-8/+8
|
* Merge pull request #6529 from niccalle/fix_typoJaime2015-10-191-1/+1
|\ | | | | DOC: Fixed a typo at line 289 at c-api.array.rst
| * DOC: Fixed a typo at line 289 at c-api.array.rstNicolas Calle2015-10-191-1/+1
| | | | | | | | Fixes #6521
* | Merge pull request #6528 from jaimefrio/fix_typoJaime2015-10-191-3/+3
|\ \ | |/ |/| DOC: fixed typo in arrays.classes.rst
| * DOC: fixed typo in arrays.classes.rstJaime Fernandez2015-10-191-3/+3
| |
* | DOC: add lib.Arrayterator to reference guide. Closes gh-6404.Ralf Gommers2015-10-111-0/+1
|/
* MAINT: cleanup dead code/arguments/fields from ufuncsNathaniel J. Smith2015-10-012-13/+5
| | | | | | | | 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...
* DOC: Document Datetime, Timedelta dtype kindsHassan Kibirige2015-09-082-0/+4
|
* ENH: add shares_memory, implement may_share_memory using itPauli Virtanen2015-08-291-0/+9
|
* DOC: Add warning that the InnerStridesArray may change.Sebastian Berg2015-08-261-0/+3
| | | | | It may be that you can say that it cannot happen when grow inner is not enabled as well.
* DOC: Fix bad rst list formats in internals.code-explanations.rst.Charles Harris2015-07-011-0/+2
| | | | The lists needed blank lines before starting.
* DOC: Remove reference to routines.ctypeslib.rst from index.rst.Charles Harris2015-07-011-1/+0
| | | | The proper reference is in routines.rst.
* DOC: Remove a reference to __array_priority__.Charles Harris2015-07-012-3/+2
| | | | Also correct its documented default value.
* DOC: Fix list markup in source/reference/arrays.ndarray.rst.Charles Harris2015-07-011-7/+8
| | | | List needs to be preceded by blank line.
* DOC: Remove references to removed setasflat ndarray method.Charles Harris2015-07-011-1/+0
|
* DOC: Fix outdated sphinx directives.Charles Harris2015-07-0110-1384/+1384
| | | | | | | Examples :cdata: -> :c:data: .. cfunction:: -> .. c:function::
* DOC: Update docs.Gabor Kovacs2015-06-211-5/+4
| | | | | | | Update docs for boolean array indexing and nonzero order. Add links to row-major and column-major terms where they appear. Closes #3177
* BUG: automatically convert recarray dtype to np.recordAllan Haldane2015-06-191-8/+10
| | | | | | | | | | | | 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
* DOC: Document '@' and matmul.Charles Harris2015-06-042-3/+18
| | | | | Document the matmul function and add '@' to the operator section of the reference manual.
* Merge pull request #5914 from sirtom67/masterCharles Harris2015-05-262-0/+12
|\ | | | | New typemap for in-place arrays of arbitrary number of dimensions:
| * New typemap for in-place arrays of arbitrary number of dimensions:Tom Krauss2015-05-252-0/+12
| | | | | | | | | | (DATA_TYPE* INPLACE_ARRAY_FLAT, DIM_TYPE DIM_FLAT) Added unittests, updated documentation.
* | DOC: add nanmedian/nanpercentile to reference docsJoris Van den Bossche2015-05-261-0/+2
|/
* Merge pull request #5605 from shoyer/stackCharles Harris2015-05-121-2/+3
|\ | | | | ENH: add np.stack
| * ENH: add np.stackStephan Hoyer2015-05-111-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | DOC: Document string dtype descriptor behaviorJaime Fernandez2015-05-061-6/+6
| |
* | MAINT: Spelling and style fixes to internals.code-explanations.rst.Charles Harris2015-04-281-63/+65
| | | | | | | | | | | | | | | | Basic cleanup of the new indexing documentation. Also replace "subspace" by "subarray" and try to clarify mixed advanced and view indexing. [skip ci]
* | DOC: Update indexing implementation explanations.Sebastian Berg2015-04-231-129/+74
| |
* | DOC: add array2string to reference guide and explain relation to array_repr/strRalf Gommers2015-03-181-0/+1
| | | | | | | | | | | | Closes gh-5684. [ci skip]
* | DOC: 'signature' preferred over 'sig' as ufunc keyword argumentJaime Fernandez2015-03-121-3/+6
| |
* | ENH: Strict checking of ufunc keyword argument namesJaime Fernandez2015-03-091-1/+1
| | | | | | | | | | | | | | 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'.
* | Merge pull request #5621 from jaimefrio/ufunc_out_tupleCharles Harris2015-03-081-1/+14
|\ \ | | | | | | ENH: ufuncs can take a tuple of arrays as 'out' kwarg
| * | ENH: ufuncs can take a tuple of arrays as 'out' kwargJaime Fernandez2015-03-081-1/+14
| | | | | | | | | | | | Closes #4752
* | | DOC: Give version when various linalg functions accepted stacked arrays.Gert-Ludwig Ingold2015-03-071-0/+2
|/ / | | | | | | | | | | Version information added in the Notes section of the functions accepting stacked arrays and in the discussion of this feature in the linalg overview.
* | ENH: add broadcast_to functionStephan Hoyer2015-02-261-0/+1
|/ | | | | | | | 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
* SWIG testing: clarify location and number of testsSandro Tosi2015-02-081-2/+2
| | | | | | | 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: Update PyArray_ArrFuncs documentationjaimefrio2015-01-291-17/+53
|
* DOC: Update docs for PyArray_FromInterface/PyArray_FromStructInterfacejaimefrio2015-01-281-7/+5
|
* Merge pull request #5249 from immerrr/add-missing-scalar-func-docsCharles Harris2015-01-261-3/+18
|\ | | | | DOC: add documentation for some scalar checks
| * DOC: add documentation for some scalar checksimmerrr2014-11-291-3/+18
| | | | | | | | DOC: Mention that PyArray_Return steals a reference to arr
View Lorry Controller Status