diff options
| author | Sebastian Berg <sebastian@sipsolutions.net> | 2022-07-10 08:12:37 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-07-10 09:12:37 -0600 |
| commit | b8163197df10c72b47edebabffac8ac0f1aac132 (patch) | |
| tree | 682814aee5044973750ad6619b4f03cb78877c9c /numpy/array_api | |
| parent | 1ba51588d767559c3fa48ed405ebc2df3ea37874 (diff) | |
| download | numpy-b8163197df10c72b47edebabffac8ac0f1aac132.tar.gz | |
DOC: Add a note about security and NumPy to the documentation (#21927)
* 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>
Diffstat (limited to 'numpy/array_api')
0 files changed, 0 insertions, 0 deletions