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
Pylint 2.0 drops support for running with Python 2 but we will still allow analysing Python 2 files. Unfortunately we sometimes use sys.version_info checks for doing different things on Python 2, such as looking for next instead of __next__. Instead of doing a check against the running environment, we should do a check against the given environment to pylint. Say for example that we'll allow this:
pylint ... -2 # Lint Python 2 files
pylint ... # by default assumes the code is Python 3
pylint ... -3 # maybe this should work as well?
The text was updated successfully, but these errors were encountered:
Looking forward to this. Using divergent PyLint on a codebase, to check for both Python2 and Python3 compatibility has proven already difficult with different levels of bug fixes in 1.9.2 and 2.0.0 with e.g. too-many-statements.
Allowing to drop supporting PyLint before 2.1 would be great.
Pylint 2.0 drops support for running with Python 2 but we will still allow analysing Python 2 files. Unfortunately we sometimes use
sys.version_info
checks for doing different things on Python 2, such as looking fornext
instead of__next__
. Instead of doing a check against the running environment, we should do a check against the given environment to pylint. Say for example that we'll allow this:The text was updated successfully, but these errors were encountered: