summaryrefslogtreecommitdiff
path: root/doc
Commit message (Collapse)AuthorAgeFilesLines
* Update doc/source/reference/arrays.dtypes.rstNathan Goldbaum2022-12-151-2/+2
| | | Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>
* DOC: update discussion in dtypes docs that references Python 2Nathan Goldbaum2022-12-151-9/+9
|
* DOC: mention installing test dependencies in testing instructionsNathan Goldbaum2022-12-142-1/+5
|
* DOC: Add minimal windows bat file for building the docsmelissawm2022-12-131-0/+74
|
* Merge pull request #22732 from ganesh-k13/add_pullMatti Picus2022-12-111-0/+4
|\ | | | | DOC: Add instruction to do `git pull`
| * DOC: Add instruction to do `git pull`ganesh-k132022-12-051-0/+4
| |
* | DOC: fix typo in basics.dispatch.rstIkko Ashimine2022-12-111-2/+2
| | | | | | overriden -> overridden
* | BUG: fix unexpected return of np.pad with mode=wrap (#22575)LU2022-12-071-0/+9
| | | | | | | | | | | | | | | | | | np.pad with mode="wrap" returns unexpected result that original data is not strictly looped in padding. This may happen in some occassions when padding widths in the same dimension are unbalanced (see added testcase in test_arraypad.py and the related issue). The reason is the function pad makes iterative calls of _set_wrap_both() in the above situation, yet period for padding is not correctly computed in each iteration. The bug is fixed by guaranteeing that period is always a multiple of original data size, and also be the possible maximum for computation efficiency. Closes #22464 Co-authored-by: Lars Grüter <lagru+github@mailbox.org>
* | DOC: Some updates to the array_api compat document (#22747)Aaron Meurer2022-12-061-3/+14
| | | | | | | | | | | | | | * Add reshape differences to the array API compat document * Add an item to the array API compat document about reverse broadcasting * Make some wording easier to read
* | Merge pull request #22707 from seberg/invalid-promotion-excSebastian Berg2022-12-053-0/+25
|\ \ | |/ |/| ENH,DEP: Add DTypePromotionError and finalize the == and != FutureWarning/Deprecation
| * DOC: typoMatti Picus2022-12-051-1/+1
| |
| * DOC: Remove last note from release note as per suggestionSebastian Berg2022-12-051-3/+2
| | | | | | | | | | | | | | | | It is a bit too obscure, but explaining that it happens for datetime unit conversions seems more detailed then useful. Updated to include a last non-indent line, which the release notes machinery doesn't like otherwise...
| * Apply suggestions from code reviewSebastian Berg2022-12-052-4/+4
| | | | | | Co-authored-by: Matti Picus <matti.picus@gmail.com>
| * DOC: Slightly expand ==/!= release note with examplesSebastian Berg2022-12-031-2/+4
| |
| * DOC: Add release note for promotion/ and ==/!= expired deprecationSebastian Berg2022-12-023-0/+24
| |
* | Merge pull request #22705 from kremeyer/devMatti Picus2022-12-021-3/+3
|\ \ | | | | | | DOC: misleading text lead to false hope
| * | DOC: misleading text lead to false hopeLaurenz Kremeyer2022-12-011-3/+3
| |/
* | Merge pull request #18535 from prithvitewatia/Issue18378Matti Picus2022-12-021-0/+7
|\ \ | | | | | | BUG: Fix <complex 0>^{non-zero}
| * | Update doc/release/upcoming_changes/18535.improvement.rstprithvitewatia2022-12-011-2/+1
| | | | | | | | | Co-authored-by: Matti Picus <matti.picus@gmail.com>
| * | Update doc/release/upcoming_changes/18535.improvement.rstprithvitewatia2022-12-011-1/+1
| | | | | | | | | Co-authored-by: Matti Picus <matti.picus@gmail.com>
| * | Apply suggestions from code reviewprithvitewatia2022-06-171-2/+2
| | | | | | | | | | | | Co-authored-by: Matti Picus <matti.picus@gmail.com> Co-authored-by: Ivan Gonzalez <scratchmex@gmail.com>
| * | Fixup release notes a bitSebastian Berg2022-06-171-3/+8
| | |
| * | Added improvement release notePrithvi2022-06-171-0/+3
| | |
* | | Remove dangling deprecation warningSyam Gadde2022-12-011-4/+0
| |/ |/| | | This deprecation is no longer mentioned elsewhere on the page.
* | DOC: Add release notes for `np.exceptions` namespaceSebastian Berg2022-11-301-0/+7
| |
* | DOC: Document exceptions and warnings in the refguideSebastian Berg2022-11-301-6/+1
| | | | | | | | | | AxisError did exist, but e.g. ComplexWarning wasn't even properly included.
* | Merge pull request #22533 from ngoldbaum/ufunc-and-function-listingSebastian Berg2022-11-293-0/+49
|\ \ | | | | | | API: Add numpy.testing.overrides to aid testing of custom array containers
| * | API: Add numpy.testing.overrides to aid testing of custom array containersNathan Goldbaum2022-11-163-0/+49
| | | | | | | | | | | | Closes #15544
* | | Merge pull request #22637 from seberg/cython_long_tRalf Gommers2022-11-281-0/+15
|\ \ \ | | | | | | | | API: (cython) remove `long_t` and `ulong_t`
| * | | API: (cython) remove `long_t` and `ulong_t`Sebastian Berg2022-11-211-0/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | They are both very confusing aliases. Unfortunately, I did not find a way to give a more informative cython compilation error. Thus, I pasted the expected error message in the hope it will be easy to google. The release notes are long and maybe confusing. I really want to prepare us for switching the default integer to (probably) `intp` and this could be rather disprutpive for Cython modules if, so I thought it might be good to hint towards that, but maybe that is too much?
* | | | ENH: Slightly improve error when gufunc axes has wrong size (#22675)Sebastian Berg2022-11-281-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * DOC: Slightly improve error when gufunc axes has wrong size My hope was to tweak it into something useful that: a @= b can raise when `b` should have two dimensions and has two axes specified but actually only has one. I didn't succeed, but I still think it a slight improvement to give the ufunc name and the actual core dimensions. * ENH: Use AxisError when gufunc axes appear wrong due to the number of entries This allows catching the error relatively targeted for in-place matmul `a @= b` which may use this path. * MAINT: Restore most TypeErrors (a bit more compexl than nice, but...) * DOC: add a release note Co-authored-by: mattip <matti.picus@gmail.com>
* | | | MAINT: npymath cleanups for isnan, isinf, isinfinite, signbit, nextafter ↵Matti Picus2022-11-281-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (#22684) * make isnan, isinf, isfinite, signbit, nextafter aliases * fixes from review Co-authored-by: Sebastian Berg <sebastianb@nvidia.com>
* | | | BLD: enable building NumPy with MesonRalf Gommers2022-11-253-36/+39
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This enables building with NumPy on Linux and macOS. Windows support should be complete to, but is untested as of now and may need a few tweaks. This contains: - A set of `meson.build` files and related code generation script tweaks, header templates, etc. - One CI job on Linux - Basic docs on using Meson to build NumPy (not yet integrated in the html docs, it's too early for that - this is for early adopters right now). The build should be complete, with the major exception of SIMD support. The full test suite passes. See gh-22546 for the tracking issue with detailed notes on the plan for switching NumPy to Meson as its build system. Co-authored-by: Stefan van der Walt <stefanv@berkeley.edu>
* | | | Merge pull request #22638 from seberg/machar-deprCharles Harris2022-11-222-0/+3
|\ \ \ \ | | | | | | | | | | DEP: Finalize MachAr and machar deprecations
| * | | | DEP: Finalize MachAr and machar deprecationsSebastian Berg2022-11-222-0/+3
| |/ / / | | | | | | | | | | | | | | | | | | | | This removes the attributes on finfo and the "public" module. It also deprecates `np.core.MachAr`. We should be able to get away with just deleting it, but there seems little reason to not just deprecate it for now.
* | | | REL: Prepare main for NumPy 1.25.0 developmentCharles Harris2022-11-2239-363/+46
| | | |
* | | | ENH: raise TypeError when arange() is called with string dtype (#22087)Daniel da Silva2022-11-211-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * ENH: raise TypeError when arange() is called with string dtype * Add release note for dtype=str change to arange() * DOC: Minor wording/formatting touchups to release note. * Update numpy/core/tests/test_multiarray.py Co-authored-by: Ross Barnowski <rossbar@berkeley.edu> * Move check to PyArray_ArangeObj * remove old code * BUG,MAINT: Clean out arange string error and other paths * BUGS: Fixup and cleanup arange code a bit * DOC: Update release note to new message * BUG: Fix refcounting and simplify arange * MAINT: Use SETREF to make arange dtype discovery more compact * MAINT: Update numpy/core/src/multiarray/ctors.c Co-authored-by: Ross Barnowski <rossbar@berkeley.edu> Co-authored-by: Sebastian Berg <sebastianb@nvidia.com> Co-authored-by: Charles Harris <charlesr.harris@gmail.com>
* | | | Merge pull request #22316 from seberg/void-strctured-newSebastian Berg2022-11-211-0/+4
|\ \ \ \ | | | | | | | | | | ENH: Allow creating structured void scalars by passing dtype
| * | | | ENH: Allow creating structured void scalars by passing dtypeSebastian Berg2022-09-211-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adds an optional `dtype=` kwarg to `np.void`. If given (and not None), this kwarg effectively turns it into: res = np.array(data, dtype=dtype)[()] Thanks for Marten's review and Bas' help with the typing. Reviewed-by: Marten van Kerkwijk <mhvk@astro.utoronto.ca> Co-authored-by: Bas van Beek <43369155+BvB93@users.noreply.github.com>
* | | | | DOC: Remove traces of interrupt handling utilitiesSebastian Berg2022-11-211-11/+0
| |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We do not use these in NumPy anymore, and at this point the whole `npy_interrupt.h` header only exists in case someone is using it out there. We may wish to just remove it at some point, vendoring the header is simple enough after all (and no known downstream usage exists). See also gh-7545, gh-12541
* | | | Merge pull request #22607 from seberg/scalar-aliasesRalf Gommers2022-11-213-1/+9
|\ \ \ \ | | | | | | | | | | DEP: Next step in scalar type alias deprecations/futurewarnings
| * | | | BUG: Fixup warning giving and remove MachAr from docsSebastian Berg2022-11-171-1/+0
| | | | |
| * | | | DOC: Document scalar type alias deprecation changes and futurewarningSebastian Berg2022-11-172-0/+9
| | | | |
* | | | | MAINT: Update main after 1.23.5 release.Charles Harris2022-11-193-0/+70
| | | | |
* | | | | DOC: testing: Fix typo: nulps -> nulpwarren2022-11-181-1/+1
| | | | | | | | | | | | | | | | | | | | [skip actions] [skip travis] [skip azp]
* | | | | DOC: Rm round_ from autosummaryInessa Pawson2022-11-171-1/+0
|/ / / /
* | | | Merge pull request #22598 from charris/update-to-focalSebastian Berg2022-11-171-0/+5
|\ \ \ \ | | | | | | | | | | MAINT, CI: Update Ubuntu 18.04 to Ubuntu 20.04
| * | | | DOC: Add compatibility release note.Charles Harris2022-11-161-0/+5
| | |/ / | |/| | | | | | | | | | We have dropped GCC-6 build testing.
* | | | DOC: expand docs on debugging with gdbNathan Goldbaum2022-11-142-9/+50
|/ / /
* | | Merge pull request #22540 from seberg/finalize-dtype-deprCharles Harris2022-11-091-0/+5
|\ \ \ | | | | | | | | DEP: Expire deprecation of dtype/signature allowing instances
View Lorry Controller Status