fix: use dev version of FindPython

[henryiii]

This is now a port, see https://gitlab.kitware.com/cmake/cmake/-/issues/24185. Based on VTK's port at https://gitlab.kitware.com/vtk/vtk/-/blob/master/CMake/patches/3.23/FindPython/Support.cmake.

Support for the correct SOABI on PyPy and the Stable ABI are included.

Closes #148.

[henryiii]

CMake Error at C:/Users/runneradmin/AppData/Local/Temp/tmpr2c79_me/build/CMakeFiles/CMakeScratch/TryCompile-1a28id/CMakeLists.txt:2 (set):
  Syntax error in cmake code at

    C:/Users/runneradmin/AppData/Local/Temp/tmpr2c79_me/build/CMakeFiles/CMakeScratch/TryCompile-1a28id/CMakeLists.txt:2

  when parsing string

    C:\hostedtoolcache\windows\Python\3.11.0\x64\Lib\site-packages\scikit_build_core\resources\find_python

  Invalid character escape '\h'.

The slashes are backwards in try-compile. I wonder if I'm injecting the wrong sort of path?

[codecov]

Codecov Report

Merging #102 (c142321) into main (bf86f79) will increase coverage by 0.05%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #102      +/-   ##
==========================================
+ Coverage   90.29%   90.34%   +0.05%     
==========================================
  Files          44       44              
  Lines        1844     1844              
==========================================
+ Hits         1665     1666       +1     
+ Misses        179      178       -1     

Impacted Files	Coverage Δ
src/scikit_build_core/settings/skbuild_model.py	100.00% <100.00%> (ø)
src/scikit_build_core/builder/builder.py	96.59% <0.00%> (+1.13%)	⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[LecrisUT]

Maybe some cmake code needs to be passed through cmake_path or on python side?

[henryiii]

@jcfr or @thewtex would you like to check this - specifically fa987eb? This applies the one relevant change in VTK's port, and a couple of changes based on usage of new features.

[jcfr]

Thanks for working on this 🙏

I should be able to review in the few days👌

[henryiii]

Okay, great. Let me know if you have any ideas for extra ways to test it; I'm already doing some basic testing, but it's not checking all paths through this file (and I think quite a few paths may never get hit due to the way we use this always knowing what Python interpreter we want). If it looks reasonable, it can go in - next version will be 0.2.

[henryiii]

Let's go ahead and put this in, and then it can be tweaked and adjusted later. I'd like to lean towards release early, release often, and get at least an dev release out for people to try in the next few days.