BUG: static typing of numpy.clip seems to be missing some kwargs #24391
Labels
Comments
|
Very much agreed yes. It's a small issue but one that can (and should) be easily fixed. |
|
Thank you very much for fixing this. Is |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the issue:
Using the 'basic type checking' option in VS code I see an error flagged on a numpy call which I believe to be incorrect. I originally posted a bug for pyright and they told me to ask here, as VS code's typing info for numpy comes from the project itself.
Reproduce the code example:
Error message:
Runtime information:
Context for the issue:
This issue is cosmetic in the sense that the code will run correctly even if the error shows in the editor.
However if you agree that it looks like the root cause is in the numpy project, I am happy to do a bit more investigation to see if it affects other ufuncs and other keyword args, and hopefully generate a PR to fix everything.
The text was updated successfully, but these errors were encountered: