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

Conversation

anirudh2290
Copy link
Member

Document _DTypeLike decision for correctness vs strictness. Please see : #16891

Depends on #16622

Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>
anirudh2290 and others added 2 commits July 21, 2020 13:54
Copy link
Member
@BvB93 BvB93 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good and #16622 has now been merged.

@BvB93 BvB93 merged commit 5b5a740 into numpy:master Aug 3, 2020
@BvB93
Copy link
Member
BvB93 commented Aug 3, 2020

Thanks @anirudh2290.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Should we error on "not-recommended" behavior in static typing tests ?
4 participants
0