[wheels] update deploys

[Gaspard-Bourgeois]

En cliquant sur copilot 'explain error" depuis l'onglet action voici ce qu'il me propose : The job failed because CMake could not find the Python3 "Development", "Development.Module", and "Development.Embed" components. Although Python 3.12.10 was detected, its development headers/libraries were missing. This error occurred at line 29 in CMakeLists.txt during the find_package(Python3 ...) step.

Solution:

1. Ensure the Python development package is installed in your CI environment. For Python 3.12 on Windows, install it with:

   pip install pybind11
   # Make sure the Python dev headers are present.

   Or, for a more robust solution, add the following to your workflow before CMake is invoked:

   - name: Add Python dev headers (Windows)
     run: |
       choco install python --version=3.12.10
       python -m pip install --upgrade pip setuptools wheel

2. Update your CMakeLists.txt to explicitly require the Development component:

   find_package(Python3 COMPONENTS Interpreter Development REQUIRED)

   If you only need the Interpreter (and not embedding or module development), remove unnecessary components.

3. If using cibuildwheel or conan, ensure the Python executable used by these tools matches the one with development headers.

Code suggestion for CMakeLists.txt:

find_package(Python3 COMPONENTS Interpreter Development REQUIRED)
# If you need Embed or Module, add them to COMPONENTS

If you need help editing the workflow or diagnosing which Python is being picked up, let me know!

Reference:

• Error at CMakeLists.txt:29 (view source).
• Full error: Could NOT find Python3 (missing: Development Development.Module Development.Embed).

Summary:
Install Python development headers and ensure CMake requests the correct components. This will resolve the "Could NOT find Python3" issue and allow the build to proceed.

[Gaspard-Bourgeois]

The job failed because CMake could not find Python3 development components—specifically, the Python3_INCLUDE_DIRS and Python3_LIBRARIES—along with Interpreter, Development, Development.Module, and Development.Embed. The error is at line 29 in CMakeLists.txt ([source](https://github.com/Julien-Livet/SymReg/blob/2200b402bf90d40513002b2ab6cd0fe51bf75222/CMakeLists.txt#L29)), and the Python interpreter (/opt/hostedtoolcache/Python/3.12.11/x64/python) cannot be run in the container.

Solution:

1. Ensure Python development headers and libraries are installed in the build container.

   • For manylinux containers, these are not always present by default.
   • Add an installation step before running CMake:

     yum install -y python3-devel

     For Python 3.12 specifically, you may need to ensure the corresponding development package is available or build Python from source with dev headers.

2. Verify the correct Python interpreter is available and executable.

   • The error shows "Cannot run the interpreter." Ensure /opt/hostedtoolcache/Python/3.12.11/x64/python is valid.
   • You may need to set the Python path explicitly:

     export Python3_ROOT_DIR=$(which python3)

   • Or set in CMake:

     set(Python3_ROOT_DIR "/usr")
     find_package(Python3 COMPONENTS Interpreter Development REQUIRED)

3. Update your workflow to use a compatible manylinux image and Python version:

   • The image quay.io/pypa/manylinux_2_28_x86_64:2025.07.27-1 may lack the required Python version or dev headers.
   • Consider switching to a standard manylinux image and installing Python manually.

Code suggestions for CMakeLists.txt:

# Ensure you request both Interpreter and Development components
find_package(Python3 COMPONENTS Interpreter Development REQUIRED)
# If you need Embed or Module, add them

Summary:
Install Python development headers (python3-devel), ensure the Python interpreter is executable in the container, and specify the correct Python root dir if needed. This will resolve the "Could NOT find Python3" error and allow the build to complete.

Reference:

• Error at CMakeLists.txt:29 (view source).

Let me know if you need the specific workflow step to add to your CI configuration!