-
Notifications
You must be signed in to change notification settings - Fork 12
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
Infinite recursion #47
Comments
pylint/astroid can produce some very deep stack traces, which may be exacerbated by pylint_protobuf but arguably not caused by it. See pylint-dev/astroid#786 in particular and pylint-dev/astroid#865 as well. |
I guess at this point I'm slowly giving up setting up pylint for the project, as it seems to dislike numpy/pandas, as I've hit way too many issues, so closing this. |
Fair enough. I think pandas has been a sore point with pylint before. If you're dropping pylint from your workflow but are still interested in checking the correctness of your protobuf integration, you should check out https://github.com/dropbox/mypy-protobuf |
Yeah, that has an issue of not supporting modules over multiple directories by the use of At this point I might as well develop in notepad. Life is hard and then we all die I guess. |
Not sure whether the issue is with pylint_protobuf or with pylint itself, but given there are some stack frames of the plugin I thought of opening the issue here first, let me know if I should open this with pylint:
Stack trace
The text was updated successfully, but these errors were encountered: