Skip to content

fix(tool): support Python 3.11 and release 2.0.1 - #7

Merged
mrgh97 merged 1 commit into
PhyAgentOS:masterfrom
mrgh97:fix/tool-python311-compatibility
Nov 20, 2026
Merged

mrgh97 merged 1 commit into
PhyAgentOS:masterfrom
mrgh97:fix/tool-python311-compatibility

Conversation

@mrgh97

@mrgh97 mrgh97 commented Nov 20, 2026

Copy link
Copy Markdown
Contributor

Enable Python 3.11 simulator processes to install and import forge-tool, and prepare the standalone forge-tool 2.0.1 release. The complete Forge workspace continues to require Python 3.12.

  • Replace Python 3.12-only aliases/generic syntax with TypeAlias and TypeVar; the ToolEndpoint wire protocol and execution lifecycle stay unchanged. Runtime alias inspection uses typing.get_args(alias).
  • Lower Tool package metadata to Python >=3.11, add a syntax compatibility guard, and update the Tool version, lockfile, release notes and both root README languages.
  • Put release source and release tooling in sibling checkouts. The existing nested checkout tripped the clean-source release guard; the regression test verifies that CI tooling is allowed while unreviewed source files still fail.

Validation:

  • Full Python 3.12 suite: 950 passed; release-line tests: 12 passed.
  • Built and validated the 2.0.1 wheel and sdist; installed that wheel in an isolated Python 3.11.18 environment: 207 Tool tests passed with the optional Arrow/Dora binding.
  • Ruff, release-version alignment and diff checks passed. Base Tool import does not eagerly import Forge Msgs or PyArrow.

Python 3.11 runtime testing was performed on macOS ARM64. This does not claim Linux Isaac Sim/RoboDojo integration validation.

@mrgh97
mrgh97 merged commit b7ab3aa into PhyAgentOS:master Nov 20, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant