[BUG]: error when attempt to build

[Falcion]

Contact details

No response

What the essence of the bug

Logs:

Downloading jupyter_core-5.9.1-py3-none-any.whl (29 kB)
Downloading tornado-6.5.2-cp39-abi3-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (443 kB)
Downloading pexpect-4.9.0-py2.py3-none-any.whl (63 kB)
Downloading ptyprocess-0.7.0-py2.py3-none-any.whl (13 kB)
Building wheels for collected packages: docopt, MarkupSafe, PyYAML, pyzmq, rpds-py
  Building wheel for docopt (pyproject.toml): started
  Building wheel for docopt (pyproject.toml): finished with status 'done'
  Created wheel for docopt: filename=docopt-0.6.2-py2.py3-none-any.whl size=13783 sha256=e74462ddd13f5d95320217b39547f0584e85eb0eabaf9760d6f30d0735a64831
  Stored in directory: /home/runner/.cache/pip/wheels/79/6f/5f/26c3d1a144117ef52122d67c32b9f3c297c3dec4fea00a31ac
  Building wheel for MarkupSafe (pyproject.toml): started
  Building wheel for MarkupSafe (pyproject.toml): finished with status 'done'
  Created wheel for MarkupSafe: filename=markupsafe-3.0.2-cp314-cp314-linux_x86_64.whl size=24203 sha256=0c27409f506d888e1d80d39e5e8e14837901f2045e521488bc4baf72bd72eb73
  Stored in directory: /home/runner/.cache/pip/wheels/31/d7/9c/91ea0a7f1bd99970c6602ae982d137132c904433343f48095b
  Building wheel for PyYAML (pyproject.toml): started
  Building wheel for PyYAML (pyproject.toml): finished with status 'done'
  Created wheel for PyYAML: filename=pyyaml-6.0.2-cp314-cp314-linux_x86_64.whl size=621848 sha256=be0a9b981c30597dcdc8771759b305b39eae3504637359b5221b837fd5ffb28e
  Stored in directory: /home/runner/.cache/pip/wheels/16/d3/3b/1f603c475e2c00f8749b9c112c874a87093b6fc1ef4a11ce07
  Building wheel for pyzmq (pyproject.toml): started
  Building wheel for pyzmq (pyproject.toml): still running...
  Building wheel for pyzmq (pyproject.toml): finished with status 'done'
  Created wheel for pyzmq: filename=pyzmq-26.2.0-cp314-cp314-linux_x86_64.whl size=733173 sha256=a3385357730e4037861c8173440c3fa1d2c2a0d46fbd24d28228309a586d4676
  Stored in directory: /home/runner/.cache/pip/wheels/a1/f7/ae/054772eb49d4c11a9a5d032eb19b1dd170ed8ed2a436e82575
  Building wheel for rpds-py (pyproject.toml): started
  Building wheel for rpds-py (pyproject.toml): finished with status 'error'
  error: subprocess-exited-with-error
  
  × Building wheel for rpds-py (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [63 lines of output]
      Running `maturin pep517 build-wheel -i /opt/hostedtoolcache/Python/3.14.0/x64/bin/python --compatibility off`
      📦 Including license file `LICENSE`
      🔗 Found pyo3 bindings
      🐍 Found CPython 3.14 at /opt/hostedtoolcache/Python/3.14.0/x64/bin/python
      📡 Using build options features from pyproject.toml
         Compiling target-lexicon v0.12.14
         Compiling python3-dll-a v0.2.10
         Compiling once_cell v1.19.0
         Compiling proc-macro2 v1.0.86
         Compiling unicode-ident v1.0.12
         Compiling libc v0.2.155
         Compiling autocfg v1.3.0
         Compiling memoffset v0.9.1
         Compiling heck v0.5.0
         Compiling triomphe v0.1.13
         Compiling pyo3-build-config v0.22.6
         Compiling archery v1.2.1
         Compiling indoc v2.0.5
         Compiling quote v1.0.36
         Compiling cfg-if v1.0.0
         Compiling syn v2.0.69
         Compiling unindent v0.2.3
         Compiling rpds v1.1.0
         Compiling pyo3-ffi v0.22.6
         Compiling pyo3-macros-backend v0.22.6
         Compiling pyo3 v0.22.6
      error: failed to run custom build command for `pyo3-ffi v0.22.6`
      
      Caused by:
        process didn't exit successfully: `/tmp/pip-install-10jg99xv/rpds-py_d92c545b5911483e8c5294fa420ce705/target/release/build/pyo3-ffi-715cc347ec2aabdc/build-script-build` (exit status: 1)
        --- stdout
        cargo:rustc-check-cfg=cfg(Py_LIMITED_API)
        cargo:rustc-check-cfg=cfg(PyPy)
        cargo:rustc-check-cfg=cfg(GraalPy)
        cargo:rustc-check-cfg=cfg(py_sys_config, values("Py_DEBUG", "Py_REF_DEBUG", "Py_TRACE_REFS", "COUNT_ALLOCS"))
        cargo:rustc-check-cfg=cfg(invalid_from_utf8_lint)
        cargo:rustc-check-cfg=cfg(pyo3_disable_reference_pool)
        cargo:rustc-check-cfg=cfg(pyo3_leak_on_drop_without_reference_pool)
        cargo:rustc-check-cfg=cfg(diagnostic_namespace)
        cargo:rustc-check-cfg=cfg(c_str_lit)
        cargo:rustc-check-cfg=cfg(Py_3_7)
        cargo:rustc-check-cfg=cfg(Py_3_8)
        cargo:rustc-check-cfg=cfg(Py_3_9)
        cargo:rustc-check-cfg=cfg(Py_3_10)
        cargo:rustc-check-cfg=cfg(Py_3_11)
        cargo:rustc-check-cfg=cfg(Py_3_12)
        cargo:rustc-check-cfg=cfg(Py_3_13)
        cargo:rerun-if-env-changed=PYO3_CROSS
        cargo:rerun-if-env-changed=PYO3_CROSS_LIB_DIR
        cargo:rerun-if-env-changed=PYO3_CROSS_PYTHON_VERSION
        cargo:rerun-if-env-changed=PYO3_CROSS_PYTHON_IMPLEMENTATION
        cargo:rerun-if-env-changed=PYO3_PRINT_CONFIG
        cargo:rerun-if-env-changed=PYO3_USE_ABI3_FORWARD_COMPATIBILITY
      
        --- stderr
        error: the configured Python interpreter version (3.14) is newer than PyO3's maximum supported version (3.13)
        = help: please check if an updated version of PyO3 is available. Current version: 0.22.6
        = help: set PYO3_USE_ABI3_FORWARD_COMPATIBILITY=1 to suppress this check and build anyway using the stable ABI
      warning: build failed, waiting for other jobs to finish...
      💥 maturin failed
        Caused by: Failed to build a native library through cargo
        Caused by: Cargo build finished with "exit status: 101": `env -u CARGO PYO3_BUILD_EXTENSION_MODULE="1" PYO3_ENVIRONMENT_SIGNATURE="cpython-3.14-64bit" PYO3_PYTHON="/opt/hostedtoolcache/Python/3.14.0/x64/bin/python" PYTHON_SYS_EXECUTABLE="/opt/hostedtoolcache/Python/3.14.0/x64/bin/python" "cargo" "rustc" "--features" "pyo3/extension-module" "--message-format" "json-render-diagnostics" "--manifest-path" "/tmp/pip-install-10jg99xv/rpds-py_d92c545b5911483e8c5294fa420ce705/Cargo.toml" "--release" "--lib"`
      Error: command ['maturin', 'pep517', 'build-wheel', '-i', '/opt/hostedtoolcache/Python/3.14.0/x64/bin/python', '--compatibility', 'off'] returned non-zero exit status 1
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for rpds-py
Successfully built docopt MarkupSafe PyYAML pyzmq
Failed to build rpds-py
error: failed-wheel-build-for-install

× Failed to build installable wheels for some pyproject.toml based projects
╰─> rpds-py
npm error code 1
npm error path /home/runner/work/Whisperer.md/Whisperer.md
npm error command failed
npm error command sh -c husky .husky/ && cd scripts/python && python3 -m venv venv && pip install -r requirements.txt
npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2025-11-01T11_11_38_565Z-debug-0.log
Error: Process completed with exit code 1.

Problem that before, we were using Python 3.13*:

Run actions/setup-python@v6
  with:
    python-version: 3.x
    check-latest: false
    token: ***
    update-environment: true
    allow-prereleases: false
    freethreaded: false
Installed versions
  (node:2096) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
  (Use `node --trace-deprecation ...` to show where the warning was created)
  Successfully set up CPython (3.13.7)

But now, since platform updated it's binaries, project uses Python 3.14*:

Run actions/setup-python@v6
  with:
    python-version: 3.x
    check-latest: false
    token: ***
    update-environment: true
    allow-prereleases: false
    freethreaded: false
Installed versions
  (node:2101) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
  (Use `node --trace-deprecation ...` to show where the warning was created)
  Successfully set up CPython (3.14.0)

Version of an project's essence

v3.0.0

On what OS you have encountered the bug.

Not important

Code of conduct

• I agree to follow this project's code of conduct

Issue policy

• I agree to follow this project's issue policy

Security policy

• I agree to follow this project's security policy.

[github-actions]

This issue is currently marked as stale due to inactivity.
If you believe it is still relevant, please provide an update or comment on this issue.