You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a clean Python 3.7 environment (which as far as I'm aware is the latest version of Python supported by pyradiomics), pip install pyradiomics is broken on Windows (and I assume most other platforms), because pyradiomics currently doesn't pin the SimpleITK version, and the SimpleITK>=2.3.0 removed Python 3.7 from packaging because Python 3.7 reached EOL in June 2023, meaning no more wheels are available and pip will default to building from the sdist. This requires building C extensions and won't work out of the box for most users.
Pyradiomics has 2 options:
Support newer versions of Python (3.8 is the oldest version SimpleITK still builds wheels for)
Pin SimpleITK==2.2.1, which is the latest version of SimpleITK with 3.7 wheels, so users don't have to manually install SimpleITK==2.2.1 manually first.
Version (please complete the following information):
OS: Windows 11
Python version: 3.7.12
PyRadiomics version [e.g. 2.2.0]
The text was updated successfully, but these errors were encountered:
Describe the bug
In a clean Python 3.7 environment (which as far as I'm aware is the latest version of Python supported by pyradiomics),
pip install pyradiomics
is broken on Windows (and I assume most other platforms), because pyradiomics currently doesn't pin theSimpleITK
version, and theSimpleITK
>=2.3.0 removed Python 3.7 from packaging because Python 3.7 reached EOL in June 2023, meaning no more wheels are available and pip will default to building from the sdist. This requires building C extensions and won't work out of the box for most users.Pyradiomics has 2 options:
SimpleITK==2.2.1
, which is the latest version of SimpleITK with 3.7 wheels, so users don't have to manually installSimpleITK==2.2.1
manually first.Version (please complete the following information):
The text was updated successfully, but these errors were encountered: