summaryrefslogtreecommitdiff
path: root/numpy/add_newdocs.py
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #8043 from pv/ufunc-copy-overlapCharles Harris2017-02-161-0/+7
|\ | | | | ENH: umath: ensure ufuncs are well-defined with memory overlapping inputs
| * DOC: fix wrong flag name docstringPauli Virtanen2017-01-231-1/+1
| |
| * ENH: core: change NPY_ITER_OVERLAP_NOT_SAME to NPY_ITER_OVERLAP_ALLOW_SAMEPauli Virtanen2017-01-191-3/+5
| | | | | | | | | | It's clearer to explicitly specify which operands are accessed elementwise, rather than to list exceptions.
| * ENH: NpyIter: add a flag to handle read/write operand overlapPauli Virtanen2017-01-191-0/+5
| | | | | | | | | | | | | | | | Add a new NPY_ITER_COPY_IF_OVERLAP iterator flag to NpyIter, which instructs it to check if read operands overlap with write operands in memory, and make temporary copies to eliminate detected overlap. Thanks to Sebastian Berg.
* | Added searchsorted to see items.Joseph Fox-Rabinovitz2017-01-311-1/+1
| |
* | DOC: Missing backticksJoseph Fox-Rabinovitz2017-01-311-1/+1
|/ | | Came across this in the online docs
* DEP: Fix escaped string characters deprecated in Python 3.6.Charles Harris2016-12-141-1/+1
| | | | | | | In Python 3.6 a number of escape sequences that were previously accepted -- for instance "\(" that was translated to "\\(" -- are deprecated. To retain the previous behavior either raw strings must be used or the backslash must be properly escaped itself.
* BUG: fix packbits and unpackbits to correctly handle empty arraysTakuya Akiba2016-12-021-1/+2
|
* DOC: Patch doc errors for atleast_nd and frombuffergfyoung2016-10-271-1/+1
| | | | | Closes gh-8214. Closes gh-8215.
* Merge pull request #8198 from eric-wieser/warning-on-accumulate-keepdimCharles Harris2016-10-231-1/+3
|\ | | | | DEP: Deprecate the keepdims argument to accumulate
| * DEP: Deprecate the keepdims argument to accumulateEric Wieser2016-10-231-1/+3
| |
* | DOC: Add missing arguments to np.ufunc.outerEric Wieser2016-10-221-1/+3
|/
* DOC: warn that dtype.descr is only for use in PEP3118Allan Haldane2016-10-181-2/+4
|
* ENH: Allows contraction order optimization in einsum function.Daniel Smith2016-09-261-5/+9
|
* ENH: a.resize(.., refcheck=True) is almost unusable on PyPyMatti Picus2016-09-171-0/+3
|
* Update add_newdocs.py (#8040)AustereCuriosity2016-09-111-1/+1
| | | DOC: Fix bad partition example.
* DOC: change version references from x.y to x.y.zPierre de Buyl2016-09-071-1/+1
|
* DOC: change Numpy to NumPy in dosctrings and commentsPierre de Buyl2016-09-061-10/+10
| | | | The strings in error messages were left untouched
* ENH: added axis param for np.count_nonzerogfyoung2016-08-041-28/+0
| | | | Closes gh-391.
* DOC: Remove a redundant theShayan Pooya2016-06-221-1/+1
|
* MAINT: Tweak documentation of broadcast.nd and broadcast.ndim.Charles Harris2016-06-171-2/+3
| | | | | | | | Note that the newly added `ndim` property is an alias for `nd` and not available in numpy versions earlier than 1.12. Add back the tests for `nd`. They can be removed if/when `nd` is dropped.
* ENH: Alias broadcast.ndim to broadcast.ndEric Wieser2016-06-151-1/+17
| | | | | Both `ndarray` and `nditer` spell this property `ndim`, so broadcast objects should too. The existing property remains for compatibility
* DOC: Further clarification of order argument in np.array.Charles Harris2016-06-121-24/+34
| | | | | Attempt to clarify the sometimes convoluted behavior of the various order options 'K', 'A', 'C', 'F'.
* DOC: Fix order='A' docs of np.arrayMechCoder2016-06-121-5/+9
|
* DOC: Fix some incorrect RST definition listsEndolith2016-05-111-4/+9
|
* DOC: link frompyfunc and vectorizeendolith2016-04-041-0/+4
|
* DOC: array link to full and full_like instead of fillMichael Seifert2016-03-221-1/+1
| | | | | ndarray.fill (not fill) is not appropriate here because it is a list how to create arrays not how to fill them. [ci skip]
* DOC: Clean up/fix several references to the "future" 1.10 releaseNathaniel J. Smith2016-01-141-1/+1
| | | | Fixes gh-7010
* DOC,BUG: Fix some latex generation problems.Charles Harris2016-01-051-16/+15
| | | | | | | | | | | | 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]
* DOC: Use print only as function when print_function is imported from __future__gfyoung2015-12-191-9/+9
| | | | Closes gh-6863.
* DEP: Stricter arg checking for array orderinggfyoung2015-12-181-4/+8
| | | | | | | | | | | | | The bug traces to the PyArray_OrderConverter method in conversion_utils.c, where no errors are thrown if the ORDER parameter passed in is not of the string data-type or has a string value of length greater than one. This commit causes a DeprecationWarning to be raised, which will later be turned into a TypeError or another type of error in a future release. Closes gh-6598.
* ENH: reimplement may_share_memory in C to improve its performancePauli Virtanen2015-11-121-0/+39
|
* Fixed a typo in np.inner docSamuel St-Jean2015-10-161-1/+1
|
* typoeulerreich2015-10-041-1/+1
|
* Document empty(..., object) initialization to None.Antony Lee2015-09-261-2/+2
| | | | | | Behavior goes back at least to 1.6.2. Fixes #6367.
* DOC: Document Datetime, Timedelta dtype kindsHassan Kibirige2015-09-081-1/+3
|
* DOC: update docs + release notes vs shares_memoryPauli Virtanen2015-08-291-3/+2
|
* ENH: add shares_memory, implement may_share_memory using itPauli Virtanen2015-08-291-7/+24
|
* Doc : fixed paramter typoSamuel St-Jean2015-08-181-1/+1
|
* DOC: Fix docstring warnings in documetation generation.Charles Harris2015-07-011-5/+9
| | | | | | | | | | | | Most of these fixes involve putting blank lines around .. versionadded:: x.x.x and .. deprecated:: x.x.x Some of the examples were also fixed.
* DOC: Remove references to removed setasflat ndarray method.Charles Harris2015-07-011-31/+0
|
* DOC: Update docs.Gabor Kovacs2015-06-211-13/+14
| | | | | | | Update docs for boolean array indexing and nonzero order. Add links to row-major and column-major terms where they appear. Closes #3177
* DOC: Document '@' and matmul.Charles Harris2015-06-041-1/+126
| | | | | Document the matmul function and add '@' to the operator section of the reference manual.
* DOC: Better document 'order' argument of 'sort' and friendsJaime Fernandez2015-05-301-6/+10
| | | | Closes #5927
* Merge pull request #5605 from shoyer/stackCharles Harris2015-05-121-1/+2
|\ | | | | ENH: add np.stack
| * ENH: add np.stackStephan Hoyer2015-05-111-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | ENH sync ndarray methods doc/args with numpy function doc/argsAllan Haldane2015-04-021-10/+11
|/ | | | | | | | | | Modified the docstrings to all, any, sum, prod, mean, var, std, min, max to add keepdims argument. Added 'out' keyword parameter to numpy.argmin, numpy.argmax, to mirror ndarray methods. Updated ndarray.clip docstring to give correct parameter description.
* Merge pull request #5307 from hunse/array-docstringCharles Harris2015-01-261-7/+7
|\ | | | | Array docstring now lists correct order default
| * DOC: array docstring lists correct order defaultEric Hunsberger2014-11-201-7/+7
| | | | | | | | Fixes #5306
* | DOC: Fixing help documentation error in numpy.zeros. Fixes #5497 [skip ci]abdulmuneer2015-01-241-1/+1
| |
View Lorry Controller Status