3.12 not build?

[nschloe]

I just wanted to try out the new Python 3.12 support. When building from gh-actions with the config

- name: Build wheels
  uses: pypa/[email protected]
  env:
    CIBW_BUILD_VERBOSITY: 3
    CIBW_PROJECT_REQUIRES_PYTHON: ">=3.7, <=3.12"
    CIBW_ENVIRONMENT: >
      CFLAGS='-s'
      CXXFLAGS='-s'
    CIBW_SKIP: "pp37* pp38*"

    CIBW_ARCHS_WINDOWS: auto64
    CIBW_ARCHS_LINUX: auto64
    CIBW_ARCHS_MACOS: x86_64 arm64

    CIBW_TEST_REQUIRES: pytest
    CIBW_TEST_COMMAND: "pytest {project}/tests/"
    CIBW_TEST_SKIP: "*-macosx_arm64"

though, I'm only getting 3.7 to 3.11. The same is true when adding

    CIBW_BUILD: cp37-* cp38-* cp39-* cp310-* cp311-* cp312-*

Any idea why that might be? (actions/setup-python has python-version 3.11.)

[Czaki]

problem is here:

    CIBW_PROJECT_REQUIRES_PYTHON: ">=3.7, <=3.12"

we use SpecifierSet from packaging and fast check shows:

In [5]: s.contains("3.12.0")
Out[5]: True

In [6]: s.contains("3.12.0b1")
Out[6]: False

Maybe you should change to:

    CIBW_PROJECT_REQUIRES_PYTHON: ">=3.7, <3.13"

[henryiii]

You should not put an upper cap on requires python at all, it’s not supported properly. Numba, which never supports the next version Python, removed it, and gets much better error messages now. https://discuss.python.org/t/requires-python-upper-limits/12663

[henryiii]

Oh, I just realized this is CIBW_PROJECT_REQUIRES_PYTHON. I wouldn’t cap that unless you know it doesn’t work and need to cap it to bump to the next cibuildwheel version. We only add new platforms on minor releases.

But it’s not harmful to cap it like it is to cap actual metadata.

[joerick]

I'd actually be curious why this was added to this project. CIBW_PROJECT_REQUIRES_PYTHON is an option that I've often wondered if we really needed to include!