8000 DOC: Add correctness vs strictness consideration for np.dtype by anirudh2290 · Pull Request #16917 · numpy/numpy · GitHub
[go: up one dir, main page]

Skip to content

DOC: Add correctness vs strictness consideration for np.dtype #16917

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Aug 3, 2020
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
MAINT: Revert static type change
  • Loading branch information
anirudh2290 committed Jul 24, 2020
commit 338b5f9c4d704700f015a99f9d9ae0c6c14a4da6
4 changes: 2 additions & 2 deletions numpy/typing/__init__.py
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@
ArrayLike
~~~~~~~~~

The ``ArrayLike`` static type tries to avoid creating object arrays. For
The ``ArrayLike`` type tries to avoid creating object arrays. For
example,

.. code-block:: python
Expand Down Expand Up @@ -78,7 +78,7 @@
dtype
~~~~~

The ``_DTypeLike`` static type tries to avoid creation of dtype objects using
The ``DTypeLike`` type tries to avoid creation of dtype objects using
dictionary of fields like below:

.. code-block:: python
Expand Down
0