-
Notifications
You must be signed in to change notification settings - Fork 23
Disallow minlength=None in dpnp.bincount
#2310
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
Conversation
|
View rendered docs @ https://intelpython.github.io/dpnp/index.html |
|
Array API standard conformance tests for dpnp=0.17.0dev6=py312he4f9c94_20 ran successfully. |
vtavana
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, @antonwolfy!
Approved however there are failed tests in Array API that are not related to this PR (relates to dpnp.linalg.qr).
I filed #2311 to investigate that. |
|
@AlexanderKalistratov, could you please review also? |
`minlength=None` was deprecated for `numpy.bincount` since numpy `1.14` and numpy is going to raise `TypeError` exception in `2.3.0` release. The PR propose to update implementation of `dpnp.bincount` and to disallow `minlength=None` in the same way as it will be implemented in NumPy 2.3.0. Additionally there is explicit type check of input arrays added through `dpnp.check_supported_arrays_type` calls at validation step. 131e4e0
minlength=Nonewas deprecated fornumpy.bincountsince numpy1.14and numpy is going to raiseTypeErrorexception in2.3.0release.The PR propose to update implementation of
dpnp.bincountand to disallowminlength=Nonein the same way as it will be implemented in NumPy 2.3.0.Additionally there is explicit type check of input arrays added through
dpnp.check_supported_arrays_typecalls at validation step.