Closed justinessert closed 3 years ago
After some troubleshooting I found that the issue does not occur when using a pandas version < 1.1.x (Specifically I tested 1.0.3 and 1.0.5).
Does anyone know if there is a specific pylint error that I could disable as an alternative workaround?
@justinessert Thank you for sharing, your information helped me a lot. I also noticed pandas 1.1.5 was released with a day, and confirmed pandas 1.1.4 doesn't raise the error. https://github.com/pandas-dev/pandas/releases
Dirty fix for now: .pylintrc
init-hook='import sys; sys.setrecursionlimit(8 * sys.getrecursionlimit())'
@justinessert @ikedaosushi @AndreiRegiani thank you all for your report/comments. I close this issue as it is a duplicate of #3939.
I am getting a RecursionError whenever I run a pylint scan on my code. I have narrowed the issue down to a Pandas merge function, though I'm not sure why that would cause an issue. This may be related to Issue 3952, though idk.
Steps to reproduce
merge.py
with the following code:pylint
,astroid
, andpandas
.pylint merge.py
.Current behavior
This causes a
RecursionError
in astroid and does not complete the pylint scan. See stack trace in the drop-down at the bottom.Expected behavior
To complete the pylint scan without an error.
pylint --version output
pylint 2.6.0 astroid 2.4.2 Python 3.7.7 (default, May 6 2020, 04:59:01)
Also, pandas version is 1.1.5
Stack Trace