chore: add 3.14 beta 1 support

[henryiii]

Trying this out.

[henryiii]

I thought the beta was showing up, but I guess testing triggered the notification. As soon as the beta is available, we should rebase and merge if it passes.

There's a warning from pluggy: pytest-dev/pluggy#573

[LecrisUT]

Epel10 hatchling:

ValueError: Unknown classifier in field `project.classifiers`: Programming Language :: Python :: 3.14

Well this will be fun. Let me check if they plan yo update it in centos. I will add a workaround until that gets resolved

[henryiii]

Windows is failing with:

LINK : fatal error LNK1104: cannot open file 'python314t.lib' 

That's on the normal 3.14 build, I didn't add a 3.14t yet.

[henryiii]

Epel10 hatchling:

ValueError: Unknown classifier in field `project.classifiers`: Programming Language :: Python :: 3.14

Well this will be fun. Let me check if they plan yo update it in centos. I will add a workaround until that gets resolved

HATCH_METADATA_CLASSIFIERS_NO_VERIFY Disables it. Though it’s actually the trove-classifiers package that needs updating, I think.

[henryiii]

On Windows, hitting:

LINK : fatal error LNK1104: cannot open file 'python314t.lib'

This isn't supposed to use the free-threaded build, though.

[henryiii]

How do you set an environment variable (HATCH_METADATA_CLASSIFIERS_NO_VERIFY) there?

[LecrisUT]

How do you set an environment variable (HATCH_METADATA_CLASSIFIERS_NO_VERIFY) there?

You can add it as

  %generate_buildrequires
+ %if 0%{rhel}
+ export HATCH_METADATA_CLASSIFIERS_NO_VERIFY=1
+ %endif
  %pyproject_buildrequires -x test,test-meta,test-numpy
  
  
  %build
+ %if 0%{rhel}
+ export HATCH_METADATA_CLASSIFIERS_NO_VERIFY=1
+ %endif
  %pyproject_wheel

Edit: added the commit with some documentation about the reason

[henryiii]

Opened upstream issue at https://gitlab.kitware.com/cmake/cmake/-/issues/26926 for Windows, also seeing it in pybind11's test suite, which doesn't use scikit-build-core.

[LecrisUT]

Weird issue. Shouldn't have this come up in 3.13 as well? Hopefully it is not github action specific.