summaryrefslogtreecommitdiff
path: root/numpy/lib
Commit message (Collapse)AuthorAgeFilesLines
...
| * | | DEP: issue deprecation warning when creating ragged array (NEP 34)mattip2019-10-311-14/+19
| | | |
* | | | ENH,DEP: Allow multiple axes in expand_dims (#14051)Larry Bradley2019-12-022-32/+59
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This PR allows the axis keyword in expand_dims to be a tuple of ints. Previously, axis could only be an int. This issue was previously discussed in gh-12290 and the changes are based on gh-12290 (comment). This PR also removes the deprecation added in v1.13 (2017-05-17), where previously axis could be outside of the range (-a.ndim - 1) <= axis <= a.ndim. Such an axis value will now raise an AxisError. Please let me know if it's too soon to remove this deprecation (I could not find any dev docs stating the length of the numpy deprecation cycle). Closes gh-12290.
* | | | BUG: warn when saving dtype with metadata (#14994)Matti Picus2019-12-022-0/+44
| | | | | | | | | | | | Address gh-14142 for the 1.18 release: warn when saving a dtype with metadata that cannot be loaded.
* | | | TST: add pytest machinery to specify memory requirements for testsPauli Virtanen2019-12-011-5/+2
| |/ / |/| |
* | | DOC: lib: Use a clearer example of ddof in the notes of the cov docstring.Warren Weckesser2019-11-301-1/+1
| | | | | | | | | | | | | | | | | | Use `ddof = 1` instead of 9, and remove a confusing comment. Closes gh-15010.
* | | DOC: Fix typo in loadtxt and genfromtxtAnis Ladram2019-11-291-2/+2
| | |
* | | DOC: Fix typo in numpy.loadtxt documentationAnis Ladram2019-11-291-1/+1
| | | | | | | | | Parameter fname: generator must return byte strings for Python 3, not Python3k.
* | | MAINT: Cleaned up mintypecode for Py3 (#14967)Joseph Fox-Rabinovitz2019-11-231-6/+4
| |/ |/| | | | | | | Using generators instead of full-blown lists Using set for search instead of list Using min to get single element insteaf of sorting full list
* | MAINT: Remove uses of scalar aliasesEric Wieser2019-11-133-17/+17
| | | | | | | | Relates to gh-6103
* | MAINT: revert gh-14800, which gave precedence to OO->O over OO->?mattip2019-11-061-6/+2
| |
* | Merge pull request #14800 from mattip/reorder-obj-comparison-loopCharles Harris2019-11-042-3/+7
|\ \ | | | | | | ENH: change object-array comparisons to prefer OO->O unfuncs
| * | ENH: add OO->? loops, use np.compare(a, b, dtype=bool), add commentsmattip2019-10-302-1/+5
| | |
| * | WIP, DEP, ENH: finish richcompare changes from 1.10mattip2019-10-292-3/+3
| |/
* | TST: Don't construct Fraction instances from numpy scalarsEric Wieser2019-10-301-2/+2
|/ | | | | | Fraction.__float__ gives a DeprecationWarning if the division results in a non-builtin float This was never intended as part of the test anyway.
* DOC: lib: Fix deprecation markup in financial function docstrings.Warren Weckesser2019-10-191-74/+77
| | | | | | | The original version doesn't render correctly; see, for example, https://numpy.org/devdocs/reference/generated/numpy.mirr.html#numpy.mirr The HTML output for the updated markup looks much better.
* Merge pull request #14629 from sethtroisi/polyfit_docRalf Gommers2019-10-181-4/+4
|\ | | | | DOC: clarify residual in np.polyfit
| * DOC: clarify residual in np.polyfitSeth Troisi2019-10-021-4/+4
| |
* | Merge pull request #14699 from mattip/doc-warningsRalf Gommers2019-10-182-16/+16
|\ \ | | | | | | MAINT: reduce the number of doc build warnings
| * | DOC: convert `None` to bare None or ``None``mattip2019-10-151-1/+1
| | |
| * | DOC: fix output argument referencemattip2019-10-151-15/+15
| |/
* | MAINT: deprecate financial functions.Warren Weckesser2019-10-162-0/+151
| | | | | | | | As per NEP-32, the financial functions are deprecated.
* | BUG: lib: Fix histogram problem with signed integer arrays.Warren Weckesser2019-10-152-5/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | An input such as np.histogram(np.array([-2, 0, 127], dtype=np.int8), bins="auto") would raise the exception ValueError: Number of samples, -1, must be non-negative. The problem was that the peak-to-peak value for the input array was computed with the `ptp` method, which returned negative values for signed integer arrays when the actual value was more than the maximum signed value of the array's data type. The fix is to use a peak-to-peak function that returns an unsigned value for signed integer arrays. Closes gh-14379.
* | Merge pull request #9301 from GuyInALabCoat/doc_editMatti Picus2019-10-151-14/+16
|\ \ | | | | | | DOC: added note to docstring of numpy.savez
| * | Use filename (vs file name) consistentlyStefan van der Walt2019-10-151-8/+8
| | |
| * | Tidy up savez keys-as-file-names languageStefan van der Walt2019-10-151-20/+8
| | |
| * | DOC: edited numpy.savez docstring note to be more specificDmytro2019-10-151-4/+13
| | | | | | | | | | | | | | | | | | | | | Note states that dictionary keys are stored as file names and may undergo unintended changes when they are not recognized as valid file names. In such cases the keys must be properly encapsulated and escaped to avoid being changed.
| * | DOC: added note to docstring of numpy.savezDmytro2019-10-151-0/+5
| |/ | | | | | | | | | | Note indicates that when used with dictionaries, savez will remove leading "/" in dictionary keys. See #9265
* | DOC: Add to doc that interp cannot contain NaN (#14598)Zijie (ZJ) Poh2019-10-151-3/+7
| | | | | | | | | | Address gh-13919 by adding to documentation that xp cannot contain NaN because its input is required to be sorted. Closes gh-13919
* | Merge pull request #14368 from jdufresne/byteswarningSebastian Berg2019-10-151-1/+1
|\ \ | |/ |/| MAINT: Avoid BytesWarning in PyArray_DescrConverter()
| * MAINT: Avoid all BytesWarningJon Dufresne2019-09-251-1/+1
| | | | | | | | | | | | | | | | A BytesWarning can be emitted when bytes are and strings are mismatched. Catching BytesWarning ensures a better boundary between str and bytes type. The test suite is now run with the -b flag to emit this warning. Fixes #9308
* | DOC misleading np.sinc() documentationSamesh Lakhotia2019-10-021-7/+0
| | | | | | | | | | | | | | The documentation currently states "It works in 2-D as well" with attached example not correct. closes #14466
* | Merge pull request #14583 from mattip/select-deprecationSebastian Berg2019-09-262-38/+10
|\ \ | |/ |/| DEP: remove deprecated select behaviour
| * DEP: remove expired deprecation in selectmattip2019-09-232-38/+10
| |
* | Merge pull request #14573 from rgommers/remove-info-filesMatti Picus2019-09-252-161/+13
|\ \ | | | | | | DOC: update submodule docstrings, remove info.py files
| * | DOC: clean up numpy.lib docstring, remove numpy/lib/info.pyRalf Gommers2019-09-222-161/+13
| |/
* | BUG: Add missing check for 0-sized array in ravel_multi_indexSebastian Berg2019-09-221-0/+18
|/ | | | | In wrap and clip modes ravel_multi_index crashes or gave invalid results if input arrays were empty but the shape not.
* TST: make xfailed test for modules in public API pass.Ralf Gommers2019-09-191-0/+3
|
* MAINT: add missing 'Arrayterator' to `numpy.lib.__all__`Ralf Gommers2019-09-191-3/+7
| | | | | | | Also finish the TODO about figuring out which np.lib.<submodule>'s are public. This is a giant mess ...
* MAINT: fix issue with `np.lib.mixins.__all__` and import of mixinsRalf Gommers2019-09-192-5/+3
|
* DOC: Added missing versionadded to diff(prepend)Joseph R. Fox-Rabinovitz2019-09-181-2/+4
|
* Merge pull request #14520 from felixdivo/patch-1Matti Picus2019-09-161-4/+3
|\ | | | | Mention that split() returns views into the original array
| * Mention that split() returns views into the original arrayFelix Divo2019-09-161-4/+3
| | | | | | Also adds a minor code change
* | Merge pull request #14521 from alexhenrie/lookforMatti Picus2019-09-161-6/+1
|\ \ | | | | | | MAINT: Simplify lookfor function
| * | MAINT: Simplify lookfor functionAlex Henrie2019-09-151-6/+1
| |/
* | Merge pull request #14511 from eric-wieser/fix-flatten_dtypeMatti Picus2019-09-162-5/+5
|\ \ | |/ |/| BUG: Fix flatten_dtype so that nested 0-field structs are flattened correctly
| * BUG: Fix flatten_dtype so that nested 0-field structs are flattened correctlyEric Wieser2019-09-142-5/+5
| | | | | | | | This affects the behavior of merge_arrays.
* | Merge pull request #14510 from eric-wieser/fix-drop_fieldsMatti Picus2019-09-152-4/+8
|\ \ | | | | | | API: Do not return None from recfunctions.drop_fields
| * | API: Do not return None from recfunctions.drop_fieldsEric Wieser2019-09-142-4/+8
| |/ | | | | | | This return value was not documented and did not make any sense. There's no reason to have a special case here.
* | Merge pull request #14508 from Kai-Striega/financial_reviewSebastian Berg2019-09-142-6/+33
|\ \ | |/ |/| DOC: Add warning to NPV function
| * TST: Move NPV-IRR congruence check to testskai-striega2019-09-142-7/+6
| | | | | | | | | | | | | | | | | | | | | | The internal rate of return (irr) is defined as the rate of return required for the net present values of a series of cashflows to be zero. i.e the lowest rate of return required for a project to break even. This is currently checked by refering to the example output from the ``irr`` and ``npv`` function documentation. This commit adds a test to confirm the identity holds.