CODEWITHSUNDEEP
pythonpylint
agiliq
agiliq

Reputation: 7758

pylint giving a number of errors with maximum recursion depth reached

Pylint gives me an error like this very frequently.

shabda@jazzy ~/uswaretech_uswaretechsite> pylint -e utpages/forms.py
No config file found, using default configuration
Exception RuntimeError: 'maximum recursion depth exceeded while calling a Python object' in <type 'exceptions.RuntimeError'> ignored

The logalib mailing list discusses it at http://lists.logilab.org/pipermail/python-projects/2009-March/001789.html , but its a old thread, so has anyone fiund an error like this with Pylint, and found the root cause in ther code?

Upvotes: 2

Views: 2973

Answers (3)

sthenault
sthenault

Reputation: 15125

This has been fixed in logilab-astng 0.20 which is out for a year and half.

Upgrading to an earlier release of pylint and logilab-astng should fix the problem.

Upvotes: 0

gurney alex
gurney alex

Reputation: 13645

This bug has been killed in the repository of logilab.astng (dependency of Pylint). You may want to update from source.

logilab-astng mercurial repository at http://www.logilab.org/cgi-bin/hgwebdir.cgi/logilab/astng

@Noufal Ibrahim: pylint tries very hard to to import your module. To my knowledge, it only does so for C extension, for which there is no Python code to analyze.

Upvotes: 1

interjay
interjay

Reputation: 110174

There's an open ticket about this bug. The bug report contains details about the cause.

Upvotes: 5

Related Questions