toolchain-health

Python version mismatches occur when mise, Poetry, and pyproject.toml specify incompatible versions. Diagnose alignment by checking all three sources, then enforce .mise.toml as the version source of truth, update pyproject.toml to a compatible range, and ensure Poetry uses the mise-managed interpreter.

Poetry version solver errors typically stem from pyproject.toml constraints that don't match the active Python interpreter or mise configuration. Validate cross-layer consistency between .mise.toml, pyproject.toml, and Poetry's environment to resolve constraint conflicts and prevent build failures.

Update Python versions when upgrading .mise.toml, editing pyproject.toml, or resolving Poetry dependency conflicts. A coherent toolchain requires synchronizing all three layers in a stepwise sequence to avoid environment errors and ensure reproducible development setups.

Yes, Poetry works with mise-managed Python by configuring Poetry to use the interpreter installed by mise. The toolchain-health approach enforces that Poetry environment points to the correct mise interpreter and validates compatibility between pyproject.toml and .mise.toml version specs.

Enforce .mise.toml as the canonical Python version source, require a compatible version range in pyproject.toml, and ensure Poetry env uses the mise interpreter. This prevents dependency conflicts, build failures, and environment drift across your development setup.

No, they don't require identical versions. .mise.toml pins the exact version, while pyproject.toml specifies a compatible range that includes it. This pattern maintains consistency while allowing Poetry flexibility for dependency resolution.