Regression: Unable to check scripts without .py-extension #219
Labels
Comments
|
Original comment by Sylvain Thénault (BitBucket: sthenault, GitHub: @sthenault?): fix explicit check of python script. Closes #219 |
|
Original comment by Sylvain Thénault (BitBucket: sthenault, GitHub: @sthenault?): Issue #247 was marked as a duplicate of this issue. |
msuozzo
pushed a commit
to msuozzo/pylint
that referenced
this issue
Feb 18, 2022
Update `pbs_for_create`, `pbs_for_set_no_merge`, `pbs_for_set_with_merge`, and `pbs_for_update` to match semantics expected by current versions of [conformance tests](googleapis/conformance-tests@0bb8520): - Rather than create separate `Write.transform` messages to hold field transforms, inline them as `update_transforms` in the main `Write.update` message (which will always be created now). Copy in the current version of the conftest JSON files and verify. Closes pylint-dev#217
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Originally reported by: BitBucket: okin, GitHub: @okin?
We are using pylint to check some standalone Python scripts that do not have an
.py-file extension.Since the update to pylint 1.2 they do not get checked anymore.
To my understanding this is because the fix for #122 introduced an check if the filename ends with
.py.The text was updated successfully, but these errors were encountered: