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
In scripts/ci.requirements.txt, we impose a specific version of Pylint, because newer versions are likely to add additional checks that fail on our code. Unfortunately, newer versions of Python can also cause failures even with the same version of Pylint. Specifically, it looks like Pylint under Python ≥3.9 becomes somewhat type-aware, and complains about subscripting Optional[something_subscriptable].
In
scripts/ci.requirements.txt
, we impose a specific version of Pylint, because newer versions are likely to add additional checks that fail on our code. Unfortunately, newer versions of Python can also cause failures even with the same version of Pylint. Specifically, it looks like Pylint under Python ≥3.9 becomes somewhat type-aware, and complains about subscriptingOptional[something_subscriptable]
.results in many errors of the form
These are all very likely to be false positives since mypy, which has a smarter type checker, is happy.
The same version of Pylint under Python ≤3.8 is happy.
The solution for this specific problem is probably to disable
unsubscriptable-object
in.pylintrc
. Let mypy do that job since it does it better.The text was updated successfully, but these errors were encountered: