Installation failure for chia-blockchain 2.5.0 using python 3.14

[clin1234]

(venv) cc@pretty:~$ pip install --extra-index-url https://pypi.chia.net/simple chia-blockchain miniupnpc
Looking in indexes: https://pypi.org/simple, https://pypi.chia.net/simple
Collecting chia-blockchain
  Using cached chia_blockchain-2.4.2.tar.gz (3.7 MB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting miniupnpc
  Downloading miniupnpc-2.2.8.tar.gz (70 kB)
  Preparing metadata (setup.py) ... done
Collecting aiofiles==23.2.1 (from chia-blockchain)
  Using cached aiofiles-23.2.1-py3-none-any.whl.metadata (9.7 kB)
Collecting anyio==4.3.0 (from chia-blockchain)
  Using cached anyio-4.3.0-py3-none-any.whl.metadata (4.6 kB)
Collecting boto3==1.34.114 (from chia-blockchain)
  Using cached boto3-1.34.114-py3-none-any.whl.metadata (6.6 kB)
Collecting chiavdf==1.1.4 (from chia-blockchain)
  Using cached chiavdf-1.1.4.tar.gz (747 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting chiabip158==1.5.1 (from chia-blockchain)
  Using cached chiabip158-1.5.1.tar.gz (125 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting chiapos==2.0.4 (from chia-blockchain)
  Using cached chiapos-2.0.4.tar.gz (1.1 MB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting clvm==0.9.10 (from chia-blockchain)
  Using cached clvm-0.9.10-py3-none-any.whl.metadata (1.6 kB)
Collecting clvm_tools==0.4.9 (from chia-blockchain)
  Using cached clvm_tools-0.4.9-py3-none-any.whl.metadata (6.3 kB)
Collecting chia_rs==0.9.0 (from chia-blockchain)
  Using cached chia_rs-0.9.0.tar.gz (223 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... error
  error: subprocess-exited-with-error
  
  × Preparing metadata (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [10 lines of output]
      💥 maturin failed
        Caused by: Cargo metadata failed. Does your crate compile with `cargo build`?
        Caused by: `cargo metadata` exited with an error: error: failed to parse manifest at `/tmp/pip-install-x5pd_6h1/chia-rs_a080ef134f5147ec92f554943ff35738/Cargo.toml`
      
      Caused by:
        no targets specified in the manifest
        either src/lib.rs, src/main.rs, a [lib] section, or [[bin]] section must be present
      Error running maturin: Command '['maturin', 'pep517', 'write-dist-info', '--metadata-directory', '/tmp/pip-modern-metadata-xgli4p9g', '--interpreter', '/home/cc/venv/bin/python3.14t']' returned non-zero exit status 1.
      Checking for Rust toolchain....
      Running `maturin pep517 write-dist-info --metadata-directory /tmp/pip-modern-metadata-xgli4p9g --interpreter /home/cc/venv/bin/python3.14t`
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

[altendky]

There are a couple things going on here. One bit is that you are running an unsupported Python version, it would seem. Python 3.14t? It would be helpful to point that out explicitly to bein with. :] Anyways, #19080 might address an aspect of this. You can try installing with pip install --extra-index-url https://pypi.chia.net/simple 'git+https://github.com/chia-network/chia-blockchain@less_than_4' miniupnpc. But... Given that's two versions ahead of what we support presently (3.9-3.12) I expect you will likely find more issues that we won't be helpful with until we get around to supporting those newer Python versions.

[emlowe]

It would be helpful if you could list or OS and python version to be sure - please provide some more details

[clin1234]

Fedora 41 with Python 3.14 free-threaded interpreter

[vvhungy]

check and make sure you install following presiquite packages:

gcc gcc-c++ gmp-devel libtool make autoconf automake openssl-devel libevent-devel boost-devel cmake

[wallentx]

Maybe kinda related, install.sh failed on Arch because I have python 3.13.1. I made some changes to install.sh and saw it fail due to pyinstaller needing to be <3.13. I bumped pyinstaller to 6.11.1 in pyptoject.toml and updated with poetry lock and reran install.sh and it all worked fine. throws an error when I run chia

From pyinstaller release notes:

3.8-3.13. Note that Python 3.10.0 contains a bug making it unsupportable by PyInstaller. PyInstaller will also not work with beta releases of Python 3.14.

EDIT: I tried forcing a bunch of stuff in chia_policy.py to get things to work with 3.13, but nothing can seem to connect to my full-node: ClientConnectorError: Cannot connect to host localhost:8555 ssl:<ssl.SSLContext object at 0x7fae3b6034a0> [None]
But apart from it not being reachable, my full-node seems to be working fine, according to the logs.
I guess some work needs to be done to get this compatible.

[github-actions]

This issue has not been updated in 14 days and is now flagged as stale. If this issue is still affecting you and in need of further review, please comment on it with an update to keep it from auto closing in 7 days.

[wjblanke]

This should get fixed in the upcoming release. It is in main but that is not pip installable.

#19080

[altendky]

pip install --extra-index-url https://pypi.chia.net/simple git+https://github.com/chia-network/chia-blockchain if someone wants. steps are being taken towards 3.13 support in #19123. there is no estimated timeline for completion of that. just need to roll through the various layers and resolve issues.

[github-actions]

This issue has not been updated in 14 days and is now flagged as stale. If this issue is still affecting you and in need of further review, please comment on it with an update to keep it from auto closing in 7 days.

[github-actions]

This issue was automatically closed because it has been flagged as stale, and subsequently passed 7 days with no further activity from the submitter or watchers.