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
@jkrinke thanks for this report. However i'm not sure this is really an issue. astroid, the inference engine used by pylint, has to evaluate some simple expression to be able to infer correctly more complex expressions. Moreover if plyint takes a long time to evaluate, then python will do so.
It may be interesting to monitor this execution time and raise a warning if it takes too much time.
@hippo91 the behaviour is problematic in a CI/CD setting where one expects that a static analysis tool would not crash (run out of memory) or not terminate.
I am currently running pylint on the above file. After 48h of run time, the process now uses 4GB of main memory. I expect that the machine would come to a grinding halt within 96h of run time. Let's assume an extremely fast processor - then pylint would crash running out of main memory within a short time. I would consider this a bug...
Steps to reproduce
v=999999999999999**999999999999999
Current behavior
Pylint seems to evaluate the expression of the assignment which will take a very long time and in the end will run out of time.
Expected behavior
Pylint should not attempt evaluation expressions.
pylint --version output
pylint 2.6.0
astroid 2.4.2
Python 3.8.6 (default, Sep 28 2020, 04:41:02)
[Clang 11.0.3 (clang-1103.0.32.62)]
The text was updated successfully, but these errors were encountered: