Skip to content

fix: sync pyproject.toml max/mojo versions with pixi.toml#241

Merged
dunnoconnor merged 1 commit intomodular:mainfrom
th0114nd:fix/pyproject-max-version
Apr 20, 2026
Merged

fix: sync pyproject.toml max/mojo versions with pixi.toml#241
dunnoconnor merged 1 commit intomodular:mainfrom
th0114nd:fix/pyproject-max-version

Conversation

@th0114nd
Copy link
Copy Markdown
Contributor

Summary

  • pyproject.toml was pinned to max==26.1.0.dev2026010820 (January 2026) while pixi.toml targets max==26.3.0.dev2026033105 (March 2026)
  • The January build introduced a breaking change where def implicitly gained raises semantics, causing parse errors (def main() raises: became a duplicate, GPU kernels became non-DevicePassable)
  • The March build resolved this by unifying def/fn semantics with neither implicitly raising — making the original puzzle code correct again
  • Users installing via uv were getting the broken January build; this fix brings pyproject.toml in sync with pixi.toml

Test plan

  • Run uv sync after this change to pull the March build
  • Verify uv run poe p01 compiles without parse errors

🤖 Generated with Claude Code

pyproject.toml was pinned to max==26.1.0.dev2026010820 (January 2026)
while pixi.toml targets max==26.3.0.dev2026033105 (March 2026). The
January build introduced a breaking change where def implicitly gained
raises semantics, causing parse errors across all puzzle files. The
March build resolved this, making the original code correct again.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@dunnoconnor dunnoconnor merged commit d170700 into modular:main Apr 20, 2026
1 check 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.

2 participants