diff options
| author | Matti Picus <matti.picus@gmail.com> | 2019-05-21 22:35:30 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-05-21 22:35:30 +0300 |
| commit | e4edcb7418cd1344e2446b75891c15111db250f1 (patch) | |
| tree | 0338a959f689d4842bf21fbd2b1c8fd19566b7bb /doc/release | |
| parent | 8eb30b49fbd9d7a0fc270c27ecf86eb70d64ac62 (diff) | |
| parent | cc5b7515b9b7a4973b7ba443cd903590d2c5a1b5 (diff) | |
| download | numpy-e4edcb7418cd1344e2446b75891c15111db250f1.tar.gz | |
Merge pull request #13463 from seberg/writable-segfault
BUG,DEP: Fix writeable flag setting for arrays without base
Diffstat (limited to 'doc/release')
| -rw-r--r-- | doc/release/1.17.0-notes.rst | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/release/1.17.0-notes.rst b/doc/release/1.17.0-notes.rst index c4c88fd20..45354eff9 100644 --- a/doc/release/1.17.0-notes.rst +++ b/doc/release/1.17.0-notes.rst @@ -33,6 +33,16 @@ The internal use of these functions has been refactored and there are better alternatives. Relace ``exec_command`` with `subprocess.Popen` and ``temp_file_name`` with `tempfile.mkstemp`. +Writeable flag of C-API wrapped arrays +-------------------------------------- +When an array is created from the C-API to wrap a pointer to data, the only +indication we have of the read-write nature of the data is the ``writeable`` +flag set during creation. It is dangerous to force the flag to writeable. +In the future it will not be possible to switch the writeable flag to ``True`` +from python. +This deprecation should not affect many users since arrays created in such +a manner are very rare in practice and only available through the NumPy C-API. + Future Changes ============== |