You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running pylint with the pylint-django plugin enabled, pylint crashes with a fatal error. This appears to be related to compatibility issues between the current version of pylint (3.3.7), dill (0.4.0), and Python 3.13.1.
Environment
Python version: 3.13.1
pylint version: 3.3.7
astroid version: 3.3.10
dill version: 0.4.0
Operating system: macOS
Steps to Reproduce
Install the dependencies: pip install pylint==3.3.7 pylint-django
Create a .pylintrc file with load-plugins=pylint_django
Run pylint on a Python file
Observe the fatal error
Expected Behavior
pylint should analyze the file without crashing
Actual Behavior
Infinite recursion in wrap_func and ignore_import_warnings_for_related_fields functions leading to:
RecursionError: maximum recursion depth exceeded
Description
When running pylint with the pylint-django plugin enabled, pylint crashes with a fatal error. This appears to be related to compatibility issues between the current version of pylint (3.3.7), dill (0.4.0), and Python 3.13.1.
Environment
Steps to Reproduce
pip install pylint==3.3.7 pylint-django
load-plugins=pylint_django
Expected Behavior
pylint should analyze the file without crashing
Actual Behavior
Infinite recursion in wrap_func and ignore_import_warnings_for_related_fields functions leading to:
RecursionError: maximum recursion depth exceeded
Traceback Summary
pylint-crash-2025-05-16-12-38-18.txt
`
Command used
Pylint output
pylint crashed with a ``AstroidError`` and with the following stacktrace:
`
Additional Information
This appears similar to previously reported issues:
2.14.5
to2.15.0
causesdjango.core.exceptions.ImproperlyConfigured
to be raised #370Temporary Workaround
I've found that commenting out
load-plugins=pylint_django
in .pylintrc allows pylint to run without crashing.The text was updated successfully, but these errors were encountered: