3.11 as max needs to be specified in pre-commit setup-cfg-fmt.

3.11 as max needs to be specified in pre-commit setup-cfg-fmt.

just read the docs of setup-cfg-fmt and saw that.

I won't bother to change this & will wait for 3.11 GA at which point, setup-cfg-fmt should be updated (or I'll do it then).
The important part is to check everything is working with 3.11 (no obvious reason why not but at least we'll know for sure).

I bumped it - it won't automatically update, the automatic classifier feature was removed from setup-cfg-fmt (I do prefer the explicit limit, though IMO this was one of the best features of setup-cfg-fmt).

IMO, this is ready to go in any time - I'd really like the trove classifier, since we support producing 3.11 wheels. Ideally, we should also be able to run on 3.11, and we can.

FYI, are we checking to make sure MACOSX_DEPLOYMENT_TARGET is set to a lower value (10.9) than the version on which the Python interpreter was compiled never shows up in our integration tests? Looks like it's showing up in https://github.com/mypyc/mypy_mypyc-wheels/actions/runs/3245210848/jobs/5322448904 (on all Pythons, actually).

IMO, this is ready to go in any time - I'd really like the trove classifier, since we support producing 3.11 wheels. Ideally, we should also be able to run on 3.11, and we can.

I would have liked for the action to be tested on 3.11 as well before getting this in (& remove the ~3.11.0-0 specifier) but fair enough, it can probably be merged in as-is.

FYI, are we checking to make sure...

I'm almost sure we don't & I think this was discussed in the past.

Any last changes on this now that 3.11 is released? It would be neat to get it in before the next cibuildwheel release with 3.11-final.