summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* DOC: consistent README.rst and docstringDimitri Papadopoulos2021-09-211-2/+2
|
* MAINT: force shebang to python2.7Dimitri Papadopoulos2021-09-214-2/+8
| | | | Make crystal clear that these remain Python 2 scripts.
* REV: 7949ba5Dimitri Papadopoulos2021-09-211-2/+2
| | | | This is a Python 2 script, revert Python 3 exception handling.
* REV: b62ffc5Dimitri Papadopoulos2021-09-211-2/+2
| | | | This is a Python 2 script, revert Python 3 exception handling.
* REV: aec0576Dimitri Papadopoulos2021-09-211-9/+10
| | | | This is a Python 2 script, fstrings are implemented in Python 3 only.
* REV: 583901aDimitri Papadopoulos2021-09-212-2/+2
| | | | | This is actually a Python 2 script, not a Python 3 script. Revert the shebang to its previous state.
* Merge pull request #19909 from BvB93/linalg-errorCharles Harris2021-09-201-0/+2
|\ | | | | MAINT: Re-export `LinAlgError` to the `np.linalg.linalg` stubs
| * MAINT: Reexport `LinAlgError` to the `np.linalg.linalg` stubsBas van Beek2021-09-201-0/+2
| |
* | Merge pull request #19893 from HaoZeke/f2py_doccleanCharles Harris2021-09-2041-622/+678
|\ \ | |/ |/| MAINT,DOC: f2py restructring
| * DOC: Address reviewer commentsRohit Goswami2021-09-205-72/+73
| |
| * DOC: Reword f2py docsRohit Goswami2021-09-207-551/+607
| |
| * MAINT: Reorder f2py doc pagesRohit Goswami2021-09-191-3/+3
| |
| * MAINT,DOC: Refactor, syntax highlighting for f2pyRohit Goswami2021-09-1938-69/+68
| |
* | Merge pull request #19907 from numpy/dependabot/pip/hypothesis-6.21.6Sebastian Berg2021-09-201-1/+1
|\ \ | | | | | | MAINT: Bump hypothesis from 6.21.1 to 6.21.6
| * | MAINT: Bump hypothesis from 6.21.1 to 6.21.6dependabot/pip/hypothesis-6.21.6dependabot[bot]2021-09-201-1/+1
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | Bumps [hypothesis](https://github.com/HypothesisWorks/hypothesis) from 6.21.1 to 6.21.6. - [Release notes](https://github.com/HypothesisWorks/hypothesis/releases) - [Commits](https://github.com/HypothesisWorks/hypothesis/compare/hypothesis-python-6.21.1...hypothesis-python-6.21.6) --- updated-dependencies: - dependency-name: hypothesis dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
* | Merge pull request #19900 from ArryanSingh/refguidefixMelissa Weber Mendonça2021-09-202-14/+11
|\ \ | | | | | | DOC: Fixed refguide errors for basics.creation.rst
| * | DOC:Fixed refguide errors for basics.creation.rstArryan Singh2021-09-202-14/+11
| | |
* | | Merge pull request #19894 from BvB93/recursive-sequenceCharles Harris2021-09-2016-288/+243
|\ \ \ | | | | | | | | ENH: Add a typing protocol for representing nested sequences
| * | | TST: Added tests for `NestedSequence`Bas van Beek2021-09-192-0/+40
| | | |
| * | | MAINT: Replace the old `_NestedSequence` union and remove `_RecursiveSequence`Bas van Beek2021-09-1913-288/+109
| | | |
| * | | ENH: Add a protocol for representing nested sequencesBas van Beek2021-09-192-0/+94
| |/ /
* | | Merge pull request #19902 from HaoZeke/refgfix_ignoreMelissa Weber Mendonça2021-09-201-0/+1
|\ \ \ | |/ / |/| | BUG,DOC: Ignore upcoming_changes from refguide
| * | BUG,DOC: Ignore upcoming_changes from refguideRohit Goswami2021-09-201-0/+1
|/ /
* | Merge pull request #19888 from WarrenWeckesser/emptylikezerostridesCharles Harris2021-09-182-0/+26
|\ \ | | | | | | BUG: core: Fix *_like strides for str and bytes dtype.
| * | BUG: core: Fix *_like strides for str and bytes dtype.warren2021-09-172-0/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When a user passed a noncontiguous array to empty_like (or any other _like function) with dtype=str or dtype=bytes, the returned array would have strides that were all 0, even though the data type was 'U1' or 'S1'. The problem was in the C code in the function PyArray_NewLikeArrayWithShape. Because the default order is "keep", the branch with the comment /* KEEPORDER needs some analysis of the strides */ was taken. That branch uses the itemsize (i.e. dtype->elsize) of the requested dtype, but for str or bytes, that itemsize is 0, so the computed strides end up being 0. It is in the subsequent call to PyArray_NewFromDescr_int that the itemsize is updated to be nonzero. The fix is to use the same check for str or bytes that is used in PyArray_NewFromDescr_int in PyArray_NewLikeArrayWithShape to figure out the itemsize when computing the strides in the KEEPORDER branch. Closes gh-19860.
* | | Merge pull request #19887 from BvB93/linalgCharles Harris2021-09-184-21/+450
|\ \ \ | | | | | | | | ENH: Add annotations for `np.linalg`
| * | | MAINT: Let `eig` and `eigvals` return a union for real inputsBas van Beek2021-09-182-9/+17
| | | | | | | | | | | | | | | | | | | | | | | | Whether an array of a `floating` or `complexfloating` dtype is returned depends on the values within in the supplied matrix. Co-Authored-By: Kevin Sheppard <bashtage@users.noreply.github.com>
| * | | TST: Add typing tests for `np.linalg`Bas van Beek2021-09-172-0/+145
| | | |
| * | | ENH: Add annotations for `np.linalg`Bas van Beek2021-09-171-20/+274
| | | |
| * | | MAINT: Move `linalg` function definitions to `linalg.linalg`Bas van Beek2021-09-172-21/+43
| |/ /
* | | Merge pull request #19890 from TheDeveloperTeam/mainCharles Harris2021-09-181-1/+1
|\ \ \ | |_|/ |/| | Added hyperlink on numpy logo
| * | Added hyperlink on numpy logoFayas Noushad2021-09-181-1/+1
|/ /
* | Merge pull request #19884 from kmod/support_pystonSebastian Berg2021-09-171-11/+6
|\ \ | |/ |/| TST: Make this sysconfig handling a bit more portable
| * TST: Make this sysconfig handling a bit more portableKevin Modzelewski2021-09-171-11/+6
|/ | | | | | | | In particular this supports Pyston, which has an additional format field in these path schemes. Instead of manually specifying which fields we think exist, do what I assume is the intention of using the default field values for everything except for the few that we want to override.
* Merge pull request #19844 from Mukulikaa/c-api-additionsCharles Harris2021-09-161-14/+61
|\ | | | | DOC: Added missing C-API functions
| * Update doc/source/reference/c-api/array.rstCharles Harris2021-09-131-1/+1
| | | | | | Co-authored-by: Melissa Weber Mendonça <melissawm@gmail.com>
| * DOC: Added missing C-API functionsMukulika2021-09-081-14/+61
| | | | | | | | | | | | | | | | 1. PyArray_CopyObject 2. PyArray_MapIterArray 3. PyArray_MapIterSwapAxes 4. PyArray_MapIterNext 5. PyArray_MapIterArrayCopyIfOverlap
* | Merge pull request #19865 from Mukulikaa/internals-doc-reorgCharles Harris2021-09-168-871/+954
|\ \ | | | | | | DOC: Moved NumPy Internals to Under-the-hood documentation for developers
| * | DOC: Moved NumPy Internals into Under-the-hood docsMukulika2021-09-138-871/+954
| | |
* | | Merge pull request #19882 from nforro/mainCharles Harris2021-09-161-5/+5
|\ \ \ | | | | | | | | MAINT: Use SHA-256 instead of SHA-1
| * | | MAINT: Use SHA-256 instead of SHA-1Nikola Forró2021-09-161-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | While the use of SHA-1 here hardly poses any risks, its use will eventually be prohibited globally in FIPS-compliant operating systems such as RHEL, and I don't see any downsides in moving away from using it. Signed-off-by: Nikola Forró <nforro@redhat.com>
* | | | Merge pull request #19883 from BvB93/moduleCharles Harris2021-09-161-0/+2
|\ \ \ \ | |/ / / |/| | | DOC: Fix the reported module names of objects in the `numpy.typing` API
| * | | DOC: Fix the module names of `numpy.typing` objectsBas van Beek2021-09-161-0/+2
|/ / /
* | | Merge pull request #19869 from mhvk/median_scalar_nanCharles Harris2021-09-144-25/+32
|\ \ \ | | | | | | | | BUG: ensure np.median does not drop subclass for NaN result.
| * | | MAINT: Improve ``_median_nancheck`` docstring.Charles Harris2021-09-141-1/+1
| | | |
| * | | MAINT: remove unused argument in private functionMarten van Kerkwijk2021-09-143-16/+15
| | | |
| * | | BUG: ensure np.median does not drop subclass for NaN result.Marten van Kerkwijk2021-09-142-8/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently, np.median is almost completely safe for subclasses, except if the result is NaN. In that case, it assumes the result is a scalar and substitutes a NaN with the right dtype. This PR fixes that, since subclasses like astropy's Quantity generally use array scalars to preserve subclass information such as the unit.
* | | | Merge pull request #19874 from ndunnewind/fix-typo-upcoming-changes-filenameCharles Harris2021-09-141-0/+0
|\ \ \ \ | |/ / / |/| | | DOC: Fix typo in upcoming changes filename
| * | | DOC: Fix typo in upcoming changes filenameNiels Dunnewind2021-09-141-0/+0
|/ / /
* | | Merge pull request #19863 from BvB93/nanquantileCharles Harris2021-09-132-80/+117
|\ \ \ | | | | | | | | BUG: Fix `nanpercentile` ignoring the dtype of all-nan arrays
View Lorry Controller Status