| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
These files should be deleted, as they were used on the SVD Tutorial which is now hosted at numpy/numpy-tutorials.
[skip azp][skip travis]
|
| |
|
|\
| |
| | |
DOC: Add C API Documentation for NPY_ITER_MULTI_INDEX
|
| | |
|
|/ |
|
|
|
|
|
|
|
| |
* Fix typo disutils -> distutils
* Update doc/source/reference/distutils_status_migration.rst
Co-authored-by: Melissa Weber Mendonça <melissawm@gmail.com>
|
| |
|
|
|
|
|
| |
[skip github]
[skip azp]
|
|\
| |
| | |
ENH: Use `threadpoolctl` in `show_runtime` (a new function)
|
| | |
|
|\ \
| | |
| | | |
CI: Test NumPy build against old versions of GCC(6, 7, 8)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Given that GCC 6 is mainly kept for Ubuntu LTS and that has 6.5
when you install gcc-6 with `apt`, let's document that as the
minimum version (also that is what is tested in CI).
[ci skip]
|
|\ \ \
| | | |
| | | | |
DOC: Reorganize user guide outline
|
| | | | |
|
|\ \ \ \
| |_|_|/
|/| | | |
DOC: Explain how to use sequences of integers as seeds.
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
CI: skip azp and circleCI logic
|
| | | | |
| | | | |
| | | | |
| | | | | |
[skip ci]
|
|\ \ \ \ \
| | | | | |
| | | | | | |
MAINT,DOC: Remove sphinx-panels in favor of sphinx-design
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Since Sphinx 5.0.0, some intersphinx links need explicit inventory names or they won't be resolved correctly. See https://www.sphinx-doc.org/en/master/changes.html\#release-5-0-0-released-may-30-2022 and https://github.com/sphinx-doc/sphinx/issues/2068.
|
| | |_|/ /
| |/| | | |
|
| |_|/ /
|/| | | |
|
|\ \ \ \
| |/ / /
|/| | | |
|
| | | |
| | | |
| | | | |
Co-authored-by: Matti Picus <matti.picus@gmail.com>
|
| | | |
| | | |
| | | | |
Co-authored-by: Rohit Goswami <r95g10@gmail.com>
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Also adds how-to-verify-bug.rst to doctest skiplist in refguide_check.
Co-authored-by: Precision Wordcraft LLC <75840094+PrecisionWordcraft@users.noreply.github.com>
Co-authored-by: Rohit Goswami <r95g10@gmail.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Rebased on local, forced push, accepted all suggestions.
Co-authored-by: Rohit Goswami <r95g10@gmail.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Initial commit for replacement PR for 17851, which was closed
when the NumPy main branch was renamed. It walks the
reader through a quick procedure for verifying bug
existence and fixes.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Fix misspelling in masked_print_option data entry and add explanation on how to
change the value.
Co-authored-by: 渡邉 美希 <miki.watanabe@watanabenoMacBook-Pro.local>
Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>
|
| | | |
| | | |
| | | |
| | | | |
Includes formatting fixes, example code corrections (not covered by refguide-check),
and updates to outdated explanations.
|
|\ \ \ \
| |_|_|/
|/| | | |
DOC: Document expectation for object array initialization
|
| | | |
| | | |
| | | |
| | | | |
Co-authored-by: Charles Harris <charlesr.harris@gmail.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This documents (and thus semi-establishes) that we try to make
sure that any array that may be *read* is fully initialized with
proper Python objects (not NULL).
However, try to write in a way that clearly says that users are not
allowed to rely on this. I somewhat suspect there are more code
paths where we may to fail fully initializing object arrays...
It does promise to regard such things as bugs, if we do not want
that, I am happy to just tell users to expect NULLs.
|
|\ \ \ \
| | | | |
| | | | | |
DOC, MAINT: Document the C-API incompatibility error and point the error message to this doc.
|
| | | | | |
|
| | |/ /
| |/| |
| | | |
| | | | |
in the error
|
|\ \ \ \
| | | | |
| | | | | |
MAINT, DOC: Update release guide
|
| |/ / / |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* DOC: Add a note about security and NumPy to the documentation
The main plan is to have something to point to when we get "security
adviseries" for issues where it is necessary to trigger very exact
bugs in impossible places, or just require direct API access to begin
with.
Neither of this is a serious security issue. I thought it might be
good to make a note that e.g. structured dtypes are a big complexity
source that one should maybe be careful about.
* DOC: Apply review suggestions
Co-authored-by: Leo Fang <leofang@bnl.gov>
* DOC: Incorporate review suggestions for security docs
Co-authored-by: Ralf Gommers <ralf.gommers@gmail.com>
* Update doc/source/reference/security.rst
Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>
* Update doc/source/reference/security.rst
Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>
Co-authored-by: Leo Fang <leofang@bnl.gov>
Co-authored-by: Ralf Gommers <ralf.gommers@gmail.com>
Co-authored-by: Charles Harris <charlesr.harris@gmail.com>
Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>
|
| | | | |
|
|\ \ \ \
| |/ / /
|/| | | |
DOC: improve description of the `data` entry in `__array_interface__`
|
| | | |
| | | |
| | | |
| | | | |
Co-authored-by: Axel Huebl <axel.huebl@plasma.ninja>.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The previous guidance on the integer type of `data` was a bit
misleading in practice and has now been improved.
In practice, Unix is fine with `int` (32bit) and `long` (64bit),
but Windows requires `long long` to hold a pointer.
https://en.cppreference.com/w/cpp/language/types
In order not to complicate the guidance, recommend the `intptr_t`
type explicitly.
|
| | | | |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
DOC: fix typo on custom array containers page
|
| | | | | |
|