Repository navigation
Add Pylint workflow for Python code analysis - #2449
nexoracontrol-ops wants to merge 1 commit into
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
sylvesterkaczmarek
left a comment
There was a problem hiding this comment.
This workflow cannot successfully lint the current TORAX tree as written. The project declares requires-python = ">=3.12", but the matrix only runs 3.8–3.10, and the job installs only pylint, not TORAX or its dependencies. That means the proposed check targets unsupported interpreters and will also emit import errors for normal imports such as JAX/Flax rather than useful project diagnostics. Could the matrix use the supported Python versions and install the project/dev extra before invoking pylint (for example, pip install -e '.[dev]')?
content/actions/how-tos/manage-workflow-runs/approve-runs-from-forks.md