test: Create pylint rule for py_binary/library targets - #330
Draft
furtib wants to merge 1 commit into
Draft
Conversation
furtib
force-pushed
the
bazel-pylint-target
branch
from
September 8, 2026 13:03
45ceee8 to
c3c23bd
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why:
We want to lint our Python files using pylint.
Bazel creates the running environment for these files inside its sandbox; therefore, we should lint these files in it.
What:
py_binaryandpy_librarytargets.Addresses:
Fixes: #225
Limitations:
Code duplication is only detected in targets of a single
pylint_testtarget.Notes:
This patch requires all Python tests to be converted into Bazel tests.
So we depend on: #329 #298 #318 and a some where migration has not even started; see: #210