I downloaded PyRadiomics using git clone https://github.com/AIM-Harvard/pyradiomics and installed it using uv sync according to the contents of “pyproject.toml” with C++ build tools of Microsoft “Build Tools for Visual Studio 2026”.
The displayed PyRadiomics version is
“pyradiomics 3.1.1.dev111+g8ed579383”
Is this safe?
It seems to be working correctly, but there’s no official information on versions above 3.1.0, which is confusing.
With the advancement of AI, malware protection is essential for “uv” and libraries in “PyPI”, so I had set the environment variable “UV_MALWARE_CHECK” to “1” before running uv sync.
Details in following URL (Sorry Japanese)
I found “pyradiomics 3.1.1.dev111+g8ed579383” by google search at following URL.
I’m not sure why the original site didn’t have a clear explanation of version 3.1.1 and how to “uv sync,” but it seems that the official information hasn’t been updated despite the content being changed to 3.1.1, resulting in an incomplete discrepancy. Alternatively, there might be a serious bug lurking in version 3.1.1 itself.
Does anyone have any more detailed information?
Personally, I’m happy that the functionality I need has been confirmed, but I think that if things continue like this, everyone won’t be able to use 3.1.1 with peace of mind.
The reason I wanted to install a standalone version of PyRadiomics—separate from 3D Slicer—is to create educational content that allows students to experience the actual process of radiomics image analysis calculations step-by-step.
Preliminary testing using Excel has already been conducted (see below).
Convolution-Radiomics-Wavelet.xlsx
I have forked the original PyRadiomics repository and named it “PyRadiomics_edu.” Aside from the added workspace folder and a minimal README file, I have left the original content entirely unchanged and plan to add the educational materials within the workspace folder.
When I downloaded the aforementioned forked “PyRadiomics_edu” repository using git clone and installed it following the same procedure with uv sync, the version became:
pyradiomics 0.1.dev1340+g15a938dad
(is not 3.1.0 , 3.1.1)
If anyone knows the reason for this, I would appreciate your guidance.
Additionally, please let me know if this practice is inappropriate, and I will delete the forked repository.
Found it!
It turned out to be the result of dynamic version management in uv, following the specifications in pyproject.toml.
“How to add dynamic versioning to uv projects”