-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Maximum recursion depth exceed numpy, chained call #2865
Comments
Actually, rather than the chained, it doesnt appear to play nicely with np.hstack and np.vstack - although I haven't pinned down precisely what arguments call it to fail. However, the above example certainly does fail for me. |
Thanks for the report @gmonkman I can reproduce it using |
@PCManticore i'm unable to reproduce it, even with |
Hey @hippo91 I can reproduce this issue with the following:
|
OK. I can reproduce it now. Thanks! |
I think the problem is due to the new |
@gmonkman this issue shoud have disappeared thanks to pylint-dev/astroid#664. |
@gmonkman i close this issue. If the problem has not disappeared with the next version of |
Steps to reproduce
Create a test.py as follows:
Run:
pylint test.py
Current behavior
Halts checking with: "internal error with sending report for module []
maximum recursion depth exceeded
Expected behavior
Does not halt checking
pylint --version output
pylint 2.3.1
astroid 2.2.5
Python 3.5.4 (v3.5.4:3f56838, Aug 8 2017, 02:17:05) [MSC v.1900 64 bit (AMD64)]
numpy 1.16.2
The text was updated successfully, but these errors were encountered: