diff options
author | Sebastian Berg <sebastian@sipsolutions.net> | 2022-06-23 10:49:29 -0700 |
---|---|---|
committer | Sebastian Berg <sebastian@sipsolutions.net> | 2022-06-23 10:57:51 -0700 |
commit | b6de7bc0dcadac314fcb9ecb6c0d59f91aadb3ed (patch) | |
tree | b723be83c4f9148ea0b3b8b93ae828e83c74618d /numpy/array_api/_array_object.py | |
parent | 441315f7e0381d93f22efc9f0d0644f72edefdcf (diff) | |
download | numpy-b6de7bc0dcadac314fcb9ecb6c0d59f91aadb3ed.tar.gz |
DOC: Document expectation for object array initialization
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.
Diffstat (limited to 'numpy/array_api/_array_object.py')
0 files changed, 0 insertions, 0 deletions