🤖 This PR was created by Repo Assist, an automated AI assistant.
Summary
The [tool.isort] section in pyproject.toml had py_version = 38, but the project's minimum supported Python version is 3.9 (set via python = ">=3.9,<3.14" in [tool.poetry.dependencies] and target-version = ['py39', ...] in [tool.black]).
Change
-py_version = 38
+py_version = 39
Why this matters
isort uses py_version to decide whether certain Python 3.9+ syntax (e.g., from __future__ import annotations behaviour) applies. Keeping it at 38 could silently produce sub-optimal import ordering for 3.9-specific constructs, and creates a mismatch with the rest of the toolchain configuration.
Test Status
- ✅
isort --check . passes with py_version = 39
- ⬜ CI will verify that no import reordering occurs on existing files (expected: no changes)
This is a one-line tooling fix with no impact on library functionality.
To route changes like this to a review issue instead of blocking, configure protected-files: fallback-to-issue in your workflow configuration.
Generated by 🌈 Repo Assist, see workflow run. Learn more.
To install this agentic workflow, run
gh aw add githubnext/agentics/workflows/repo-assist.md@11c9a2c442e519ff2b427bf58679f5a525353f76
🤖 This PR was created by Repo Assist, an automated AI assistant.
Summary
The
[tool.isort]section inpyproject.tomlhadpy_version = 38, but the project's minimum supported Python version is 3.9 (set viapython = ">=3.9,<3.14"in[tool.poetry.dependencies]andtarget-version = ['py39', ...]in[tool.black]).Change
Why this matters
isortusespy_versionto decide whether certain Python 3.9+ syntax (e.g.,from __future__ import annotationsbehaviour) applies. Keeping it at 38 could silently produce sub-optimal import ordering for 3.9-specific constructs, and creates a mismatch with the rest of the toolchain configuration.Test Status
isort --check .passes withpy_version = 39This is a one-line tooling fix with no impact on library functionality.
Warning
Protected Files
This was originally intended as a pull request, but the patch modifies protected files. These files may affect project dependencies, CI/CD pipelines, or agent behaviour. Please review the changes carefully before creating the pull request.
Click here to create the pull request once you have reviewed the changes
Protected files
pyproject.tomlTo route changes like this to a review issue instead of blocking, configure
protected-files: fallback-to-issuein your workflow configuration.