-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pylint 2.8.2 broke pylint-quotes #4420
Comments
Hello, thank you for the report. We changed the tuple from int to string because we can't be sure that we're capable of getting the version from |
Okay, but that was a breaking change for plugin developers, and as such I'm not entirely sure why this was released as PATCH version, and not at least MINOR. See: https://semver.org/#what-if-i-inadvertently-alter-the-public-api-in-a-way-that-is-not-compliant-with-the-version-number-change-ie-the-code-incorrectly-introduces-a-major-breaking-change-in-a-patch-release The |
Personally I would advise to just use black or another auto-formatter. Flake8 had a lot of check to not use |
Btw 2.8 was the minor that removed it, we added it back in a patch. |
We need to be able to handle empty version for tests. Closes #4420
Steps to reproduce
See edaniszewski/pylint-quotes#24
See
pylintrc
in attached pylint_bug.zippython -m venv venv . venv/bin/activate pip install -r requirements.txt pylint --rcfile pylintrc demo.py
Current behavior
Running this configuration on a file containing:
results in an exception:
Expected behavior
pylint
should not throw exceptions, and instead generate report complaining about the use of double quotes (""
) and illegal variable namefoo
.pylint --version output
Result of
pylint --version
output:Additional dependencies:
Probable cause:
pylint
seems to have just changed versioning scheme: pylint-2.8.1...v2.8.2The text was updated successfully, but these errors were encountered: