[SCSB-170] pin Python<3.13

[zacharyburnett]

Resolves SCSB-170

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.95%. Comparing base (d4af8fd) to head (e50b818).
Report is 46 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #139   +/-   ##
=======================================
  Coverage   89.95%   89.95%           
=======================================
  Files          17       17           
  Lines        1792     1792           
=======================================
  Hits         1612     1612           
  Misses        180      180           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[schlafly]

I'm merging this since it resolves the build failures, but I'm confused about the content of the PR, which looks more like "build wheels for python != 3.13" and the title of the PR (pin python <3.13).

[zacharyburnett]

I'm merging this since it resolves the build failures, but I'm confused about the content of the PR, which looks more like "build wheels for python != 3.13" and the title of the PR (pin python <3.13).

Oh sorry! I was working with a very similar PR in another tab and must have gotten them confused.

[schlafly]

Sounds good, thanks. Do you understand the issue? Somehow I expect python 3.13 problems to manifest as syntax errors or unit test errors and not only in compiling the binaries, but maybe if cython isn't happy with 3.13 then it might only appear when building wheels.

[zacharyburnett]

Sounds good, thanks. Do you understand the issue? Somehow I expect python 3.13 problems to manifest as syntax errors or unit test errors and not only in compiling the binaries, but maybe if cython isn't happy with 3.13 then it might only appear when building wheels.

I don't understand the issue, but from further experimentation with cibuildwheel yesterday I think we should revert this change and instead pin Python in pyproject.toml until we can figure out why it's failing; that will be much more maintainable and also prevent users from trying to install on 3.13 and getting installation errors.

I'll make another PR