Add support for py3.13 and py3.14

[tpaviot]

Summary by Sourcery

Add CI and conda-build support for Python 3.13 and 3.14 across all platforms and update build configuration for modern Python and toolchain compatibility.

New Features:

• Declare python_abi run and host dependencies for Python 3.13 and 3.14 in the conda recipe to support these interpreters.

Enhancements:

• Update CMake Python installation path detection to use sysconfig platlib paths compatible with newer Python versions.
• Replace deprecated swig_link_libraries usage with target_link_libraries for all SWIG-generated Python modules.
• Set an explicit macOS deployment target in the conda CMake build script to improve compatibility with older macOS versions.

Build:

• Extend Azure Pipelines conda-build jobs to build against Python 3.13 and 3.14 on Windows, macOS, and Ubuntu 24.04.
• Adjust conda-build environment creation to use a fixed Python 3.12 bootstrap while passing the target Python version explicitly to conda-build.

CI:

• Add matrix entries in azure-pipelines to run conda-build for Python 3.13 and 3.14 on all supported OS images.

Tests:

• Adjust conda test requirements to use more specific Qt bindings and updated versions for Windows test environments.

[sourcery-ai]

Reviewer's Guide

This PR adds CI and conda-build support for Python 3.13 and 3.14, updates the CMake build to use modern Python introspection and link APIs, and refines the conda recipe and build scripts to better support newer Python and macOS targets.

Flow diagram for updated conda build.sh and CMake configuration

flowchart TD
  Start([Start build.sh]) --> DetectOS

  DetectOS["Check uname"] -->|Darwin| SetExtra["Set EXTRA_CMAKE_ARGS = -DCMAKE_OSX_DEPLOYMENT_TARGET=10.13"]
  DetectOS -->|Other| ClearExtra["Set EXTRA_CMAKE_ARGS = empty"]

  SetExtra --> Configure
  ClearExtra --> Configure

  Configure["Run cmake -G Ninja with:\n CMAKE_BUILD_TYPE=Release\n CMAKE_PREFIX_PATH=$PREFIX\n CMAKE_INSTALL_PREFIX=$PREFIX\n Python3_FIND_STRATEGY=LOCATION\n Python3_FIND_FRAMEWORK=NEVER\n SWIG_HIDE_WARNINGS=ON\n PYTHONOCC_MESHDS_NUMPY=ON\n EXTRA_CMAKE_ARGS"] --> Build

  Build["Run ninja"] --> Install

  Install["Run ninja install"] --> End([End build.sh])

Loading

File-Level Changes

Change	Details	Files
Add Azure Pipelines jobs and conda-build plumbing for Python 3.13 and 3.14 on all supported OSes.	Extend azure-pipelines.yml to include conda-build.yml template invocations for py3.13 and py3.14 on Ubuntu, macOS, and Windows images. Adjust conda-build.yml so build_env always uses Python 3.12 but passes the desired Python version via --python to conda-build for each job.	azure-pipelines.yml conda-build.yml
Update CMake Python integration to use sysconfig and standard target_link_libraries instead of deprecated helpers.	Replace distutils.sysconfig-based logic with sysconfig.get_path('platlib') and os.path.relpath to compute PYTHONOCC_INSTALL_DIRECTORY. Switch from swig_link_libraries to target_link_libraries for all SWIG-generated Python modules, keeping the same linked OCCT and Python3::Module targets, including Cocoa.framework on macOS.	CMakeLists.txt
Improve conda build scripts and metadata for compatibility with newer Python versions and macOS.	Introduce EXTRA_CMAKE_ARGS in ci/conda/build.sh to set CMAKE_OSX_DEPLOYMENT_TARGET=10.13 on Darwin and forward it to CMake, while simplifying by removing dead rpath-fix code. Add python_abi run/host dependencies for Python 3.13 and 3.14 selectors and modernize test-time GUI deps by replacing generic pyqt/wx/pyside entries with platform-specific pyqt5-sip, pyside6>=6.10, wxpython>=4.2, and svgwrite>=1.4.	ci/conda/build.sh ci/conda/meta.yaml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• In CMakeLists.txt, the new execute_process uses sys.prefix instead of ${CMAKE_INSTALL_PREFIX} as the base for relpath, which changes the semantics from the previous distutils-based code and may produce incorrect install paths when CMAKE_INSTALL_PREFIX differs from the Python prefix.
• In conda-build.yml, the build environment is now always created with python=3.12 even for 3.13/3.14 builds, while conda-build is invoked with --python set to the requested version; consider aligning the environment Python version with py_maj/py_min unless there is a specific reason to decouple them.
• The new Azure pipeline job templates have minor inconsistencies (double spaces in - template: conda-build.yml and job names like macOS_12_python313 using vmImage: 'macOS-latest' which is no longer 12); cleaning these up will make the configuration clearer and less confusing.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- In CMakeLists.txt, the new `execute_process` uses `sys.prefix` instead of `${CMAKE_INSTALL_PREFIX}` as the base for `relpath`, which changes the semantics from the previous distutils-based code and may produce incorrect install paths when `CMAKE_INSTALL_PREFIX` differs from the Python prefix.
- In `conda-build.yml`, the build environment is now always created with `python=3.12` even for 3.13/3.14 builds, while `conda-build` is invoked with `--python` set to the requested version; consider aligning the environment Python version with `py_maj/py_min` unless there is a specific reason to decouple them.
- The new Azure pipeline job templates have minor inconsistencies (double spaces in `- template:  conda-build.yml` and job names like `macOS_12_python313` using `vmImage: 'macOS-latest'` which is no longer 12); cleaning these up will make the configuration clearer and less confusing.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}