-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
numpy comparison-with-callable / no-member confusion #2784
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
numpy comparison-with-callable / no-member confusion #2784
Comments
This and #2694 lead me to believe that pylint would greately benefit from a continuous build having tests for simple code using numpy. |
Thanks for the report, this is fixed in astroid's master. While having some simple tests with |
Thank you. When would the Astroid fix make it into a release? A project I'm working on has been blocked from upgrading pylint for a while due to the successive regressions with numpy. |
…ransform Turns out that this was conflicting with the `any` builtin, while the original intention was to return a value that cannot be inferred, until we have support for types. This should fix a couple of false positives on pylint's side where the return value of numpy functions was considered to be itself a function. Close pylint-dev/pylint#2784
Just released astroid 2.2.3 with this fix. Sorry to hear that, do you have by any chance a list of regressions that caused you to be blocked? Would be great to open some issues for them if we don't have them already opened. |
Thank you for making another release. I just had some concern that the release might take a while as for #2694. |
….2.3 What's New in astroid 2.2.3? ============================ Release Date: 2019-03-03 * Replace `any` with `uninferable` when returning values from `numpy` transform Turns out that this was conflicting with the `any` builtin, while the original intention was to return a value that cannot be inferred, until we have support for types. This should fix a couple of false positives on pylint's side where the return value of numpy functions was considered to be itself a function. Close pylint-dev/pylint#2784
appears to be a recent regression
e.g.:
and
pylint --version output
numpy 1.16.2
The text was updated successfully, but these errors were encountered: