check-python-compat

To check Python compatibility across 3.10 to 3.12, scan your codebase for incompatible imports, syntax, typing constraints, and behavioral differences using a compatibility table, then review the generated remediation notes. This process validates projects declaring constraints in pyproject.toml.

When upgrading Python from 3.10, look for incompatible imports like tomllib or tomli, changes to datetime.fromisoformat, and typing improvements. Static analysis can detect these behavioral differences and syntax constraints to prevent runtime failures on 3.11 or 3.12.

Yes, validating the pyproject.toml requires-python constraint ensures code runs reliably on target Python versions. By reading project constraints and scanning for affected features, you can enforce detection of incompatible imports and typing limitations across 3.10 to 3.12.

To fix Python typing and import errors found during a 3.12 compatibility check, apply the concrete remediation steps provided by the analysis. These fixes address incompatible imports and typing constraints by referencing the compatibility table for the targeted environment.

The best way to automate Python 3.10-3.12 compatibility checks before a release is to run a static analysis workflow that reads your pyproject.toml constraints and scans for incompatible syntax and modules. This surfaces version issues and provides targeted fixes.

Your Python code fails with tomllib or datetime.fromisoformat imports due to behavioral differences and module availability across 3.10 to 3.12. Running a compatibility check detects these specific incompatible imports and provides concrete remediation notes.