summaryrefslogtreecommitdiff
path: root/numpy
Commit message (Collapse)AuthorAgeFilesLines
* MAINT: Disable test_blas64_dot.Charles Harris2021-07-151-4/+5
| | | | | | | This test is failing due to system oom during amd64 wheel tests with ILP64 OpenBLAS. Should not be run on account of memory restrictions, but evidently those are not reliably reported to the docker container running the tests.
* Merge pull request #19151 from czgdp1807/stack_matMatti Picus2021-07-143-66/+870
|\ | | | | ENH: Vectorising np.linalg.qr
| * removed redudancy in codeczgdp18072021-07-102-44/+20
| |
| * removed redundant functionsczgdp18072021-07-091-67/+49
| |
| * fixed linting issuesczgdp18072021-06-241-4/+5
| |
| * addressed C reviewsczgdp18072021-06-241-33/+8
| |
| * Addressed testing reviewsczgdp18072021-06-242-20/+24
| |
| * refactoring completeczgdp18072021-06-221-145/+60
| |
| * factored out common init parts for sorgqr, dorgqrczgdp18072021-06-221-109/+57
| |
| * updated method for finding optimal work_countczgdp18072021-06-091-9/+21
| |
| * shifted qr code in umath_linalg.c.src aboveczgdp18072021-06-091-426/+425
| |
| * Take work_count as it isczgdp18072021-06-091-6/+6
| |
| * fixed title line in release notesczgdp18072021-06-081-6/+0
| |
| * Addressed reviewsczgdp18072021-06-082-3/+10
| |
| * removed debug prints and addressed reviewczgdp18072021-06-072-5/+0
| |
| * documentation fixczgdp18072021-06-051-2/+2
| |
| * resolved linting issuesczgdp18072021-06-051-1/+1
| |
| * resolved linting issuesczgdp18072021-06-051-1/+2
| |
| * removed trailing white spacesczgdp18072021-06-053-21/+21
| |
| * linting issue fixedczgdp18072021-06-051-1/+2
| |
| * documentation updatedczgdp18072021-06-051-8/+20
| |
| * tests for stacked inputs addedczgdp18072021-06-051-0/+61
| |
| * existing tests passedczgdp18072021-06-052-24/+57
| |
| * moving intialization outside the loopczgdp18072021-06-051-5/+6
| |
| * ready for formal addition of tests and documentation updateczgdp18072021-06-042-55/+280
| |
| * WIPczgdp18072021-06-042-58/+407
| |
| * ENH: r, raw, economic now accept stacked matricesczgdp18072021-06-032-22/+335
| |
* | Merge pull request #19316 from arubiales/quit_runtimewarning_moduleop_Matti Picus2021-07-143-90/+51
|\ \ | | | | | | BUG: Fix warning problems of the mod operator
| * | TST: Ignore floating point warning tests on MacOSSebastian Berg2021-07-121-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | It is very much possible that this will also fail on other systems and should rather only run, e.g. on newer glibc versions. In principle, we could also split this into "no warnings given" and "warning given". MacOS seems very sloppy with floating point warnings, but hopefully it at least does not give spurious ones.
| * | BUG: Fix floating point error flags in division related opsSebastian Berg2021-07-123-71/+28
| | |
| * | TST: Change tests to more strictly (correctly) check for errorsSebastian Berg2021-07-121-11/+17
| | | | | | | | | | | | | | | | | | The old tests seems not to have noticed all types of errors here. It seems the `assert_no_warnings` context does not care about exceptions.
| * | delete comment about warningrubiales2021-07-121-1/+0
| | |
| * | Fix 1 test_umath and npy_math_internalrubiales2021-07-122-1/+17
| | |
| * | Solved test fails due to the warnings changed #18170rubiales2021-07-122-6/+5
| | |
| * | solve the problems of mod operator except for infinite values #18170rubiales2021-07-121-23/+1
| | |
* | | DOC: fix see also references in numpy.resize (#19475)Niko Savola2021-07-141-3/+3
| | |
* | | Merge pull request #19447 from 1fish2/show_config_docstringMatti Picus2021-07-131-0/+24
|\ \ \ | |/ / |/| | DOC: BLAS/LAPACK linking rules
| * | review feedbackJerry Morrison2021-07-121-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | * Accelerate in "NumPy 1.21+". I thought the NumPy 1.20.0 release note decommissioned "the Accelerate library as a candidate" but it doesn't mention BLAS. https://github.com/numpy/numpy/pull/15759/files#diff-6fde01624b4d27874d419c0f8aeae3743c4f5e7e1c9f2b039eb453a714d0cbb1R396 seems to affect both but
| * | Update numpy/distutils/misc_util.py Jerry Morrison2021-07-121-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `:numpy:` Thanks, Matti! Can you illuminate what the colons do in pip install? The doc webpage and CLI help says: > Accepts either ":all:" to disable all binary packages, ":none:" to empty the set (notice the colons), or one or more package names with commas between them **(no colons).** Co-authored-by: Matti Picus <matti.picus@gmail.com>
| * | code review iterationJerry Morrison2021-07-121-18/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Give the OS-specific site-packages directories for NumPy's OpenBLAS. * Include the `pip install numpy --only-binary numpy` variation, but not `:numpy:` since pip install doesn't document that. `pip install --only-binary numpy numpy` also works but that's confusing to parse. * Drop the sentence on the Accelerate bug on macOS < 11.3 since this isn't the place for it. * Also drop the search-order part about Accelerate? This applies to Numpy 1.19 as well as 1.21+. * Clarify the part about finding external BLAS/LAPACK libs. Some doc should explain what people need to know about installation. If they need portable, reproducible results, they should probably use the same BLAS/LAPACK libs compiled with the same compiler everywhere. It's unfortunate to install NumPy + SciPy linked to Accelerate, along with more pips, only to discover that NumPy won't load on their Mac and have to start over. Or will SciPy reject the older LAPACK API and have problems using different BLAS/LAPACK libs? Installing pips in Docker takes over an hour (vs. 15 minutes) if linking NumPy and SciPy to an external BLAS/LAPACK (and another pip conditionally compiles from source if NumPy did). Worse to have to debug CI failures because their CI on Linux computes different output than Accelerate. Should this also explain how to tell which release of OpenBLAS is included in a NumPy installation? (What got us into installing NumPy from source was needing an OpenBLAS bug fix release.)
| * | apply suggestions to the wheel caseJerry Morrison2021-07-121-7/+6
| | |
| * | fix ")" positionJerry Morrison2021-07-101-1/+1
| | |
| * | Document BLAS/LAPACK linking rulesJerry Morrison2021-07-091-0/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ... per recent numpy-discussion@python.org discussion. My aim was to explain the rules clearly including background that developers might need to learn. I made some guesses to fill in details. For sure let me know whatever's wrong or unclear here. Should the website installation page https://numpy.org/install/ link to this doc so developers can learn how to install NumPy for their situation?
* | | MAINT: Avoid unicode characters in division SIMD code commentsSebastian Berg2021-07-121-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This avoids unicode characters in the division SIMD code to circumvent problems reading the utf-8 encoded file in windows. The proper fix is probably to just assume utf-8 and feel free to use unicode characters in `c.src` files. But here, it doesn't matter too much to just avoid utf-8 quickly. See gh-19454
* | | Merge pull request #19445 from timhoffm/doc-broadcast_toMatti Picus2021-07-121-2/+3
|\ \ \ | | | | | | | | DOC: broadcast_to() supports int as shape parameter
| * | | DOC: broadcast_to() supports int as shape parameterTim Hoffmann2021-07-091-2/+3
| |/ /
* | | TST: Fix a `GenericAlias` test failure for python 3.9.0Bas van Beek2021-07-121-1/+8
| | |
* | | Merge pull request #19440 from czgdp1807/refacMatti Picus2021-07-122-287/+140
|\ \ \ | | | | | | | | MAINT: factored out _PyArray_ArgMinMaxCommon
| * | | fixed linting issuesczgdp18072021-07-101-4/+7
| | | |
| * | | tests refactoredczgdp18072021-07-101-140/+108
| | | |
View Lorry Controller Status