$ the-wire · showcase
Google Cloud Python tools sync lint and format
By RepoJournal · Filed · About Google
The googleapis/google-cloud-python repo closed a gap where code could pass lint checks but fail after running the formatter, tightening consistency for generated libraries.
The googleapis/google-cloud-python repo closed a gap where code could pass lint checks but fail after running the formatter. The fix [1] adds an import-ordering check to lint, and the pre-commit config now includes a `ruff-format` hook [2], so local commits and CI lint agree. This synchronization rolls out to generated libraries after the next generation cycle. On the JAX side, a fix [3] repairs the transitive dependency graph error that was breaking `bazel mod show_repo --all_repos`, restoring an important debugging tool. The python-genai SDK added a `destination` parameter to `client.files.download` [4] to support streaming downloads to disk or file-like objects, and exposed `ProcessingCallStep` and `ProcessingResultStep` in the Interactions SDK [5].
Action items
- → Run the new lint import-order check on google-cloud-python PRs before pushing googleapis/google-cloud-python [immediate]
- → Test `bazel mod show_repo --all_repos` on the JAX head to confirm the transitive dependency fix google/jax [plan]
- → Review python-genai docs for the new `destination` parameter in `client.files.download` googleapis/python-genai [plan]
References
- [1] chore: fix inconsistency between lint and format ↗ googleapis/google-cloud-python
- [2] chore: add ruff format hook to pre-commit config (#18244) ↗ googleapis/google-cloud-python
- [3] Fix the transitive dependency graph error ↗ google/jax
- [4] feat: Add destination parameter to client.files.download to support streaming downloads to disk or file-like objects ↗ googleapis/python-genai
- [5] fix: expose ProcessingCallStep and ProcessingResultStep in Interactions SDK ↗ googleapis/python-genai