Skip to content
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

Closed
gmonkman opened this issue Apr 13, 2019 · 8 comments
Closed

Maximum recursion depth exceed numpy, chained call #2865

gmonkman opened this issue Apr 13, 2019 · 8 comments
Assignees
Labels
Astroid Related to astroid Bug 🪲 Crash 💥 A bug that makes pylint crash

Comments

@gmonkman
Copy link

gmonkman commented Apr 13, 2019

Steps to reproduce

Create a test.py as follows:

import numpy
A = numpy.array([[1,2,3],[2,3,4]])
B = numpy.array([[1,2,3],[2,3,4]])
C = numpy.vstack((A,B)).T

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

@gmonkman
Copy link
Author

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.

@PCManticore
Copy link
Contributor

Thanks for the report @gmonkman I can reproduce it using --extension-pkg-whitelist=numpy

@PCManticore PCManticore added Astroid Related to astroid Bug 🪲 Crash 💥 A bug that makes pylint crash labels Apr 19, 2019
@hippo91
Copy link
Contributor

hippo91 commented Apr 21, 2019

@PCManticore i'm unable to reproduce it, even with --extension-pkg-whitelist=numpy.
What version of numpy did you use?

@PCManticore
Copy link
Contributor

Hey @hippo91 I can reproduce this issue with the following:

pylint 2.4.0-dev0
astroid 2.3.0
Python 3.5.5 (default, Apr  5 2018, 08:18:31)
[GCC 4.2.1 Compatible Apple LLVM 8.1.0 (clang-802.0.42)]
numpy==1.16.3

@hippo91
Copy link
Contributor

hippo91 commented Apr 23, 2019

OK. I can reproduce it now. Thanks!

@hippo91 hippo91 self-assigned this Apr 23, 2019
@hippo91
Copy link
Contributor

hippo91 commented Apr 23, 2019

I think the problem is due to the new array_function_dispatch decorator in the numpy 1.16 version.

@hippo91
Copy link
Contributor

hippo91 commented Aug 31, 2019

@gmonkman this issue shoud have disappeared thanks to pylint-dev/astroid#664.
Can you confirm please? So That i could close this issue.

@hippo91
Copy link
Contributor

hippo91 commented Sep 6, 2019

@gmonkman i close this issue. If the problem has not disappeared with the next version of astroid do not hesitate to open it again. Thanks.

@hippo91 hippo91 closed this as completed Sep 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Astroid Related to astroid Bug 🪲 Crash 💥 A bug that makes pylint crash
Projects
None yet
Development

No branches or pull requests

3 participants