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
We just re-tested the installation in a clean environment (Python 3.12), and it installs successfully on our side.
If umap==0.1.1 cannot be resolved in your environment, you can safely comment out or remove that line from requirements_domain.txt, as it is not required for the main workflow.
Let us know if the issue persists.
Activity
YoungDubbyDu commentedon Feb 27, 2026
Thanks for trying it out!
We are currently running MLEvolve with Python 3.12, and it works in our setup.
Could you please share the full error trace you encountered? That will help us reproduce and diagnose the issue.
zucanlv commentedon Feb 27, 2026
ERROR: Ignored the following versions that require a different python version: 0.10.0 Requires-Python >=3.7,<3.10; 0.10.1 Requires-Python >=3.7,<3.10; 0.11.0 Requires-Python >=3.7,<3.10; 0.11.1 Requires-Python >=3.7,<3.10; 0.11.2 Requires-Python >=3.7,<3.10; 0.11.3 Requires-Python >=3.7,<3.10; 0.11.4 Requires-Python >=3.7,<3.10; 0.12.0 Requires-Python >=3.7,<3.10; 0.12.1 Requires-Python >=3.7,<3.10; 0.13.0 Requires-Python >=3.7,<3.11; 0.13.1 Requires-Python >=3.7,<3.11; 0.13.2 Requires-Python >=3.7,<3.11; 0.13.3 Requires-Python >=3.7,<3.11; 0.13.4 Requires-Python >=3.7,<3.11; 0.14.0 Requires-Python >=3.7,<3.11; 0.14.1 Requires-Python >=3.7,<3.11; 0.15.0 Requires-Python >=3.7,<3.11; 0.15.1 Requires-Python >=3.7,<3.11; 0.16.0 Requires-Python >=3.7,<3.11; 0.16.1 Requires-Python >=3.7,<3.12; 0.17.0 Requires-Python >=3.7,<3.12; 0.17.1 Requires-Python >=3.7,<3.12; 0.17.2 Requires-Python >=3.7,<3.12; 0.18.0 Requires-Python >=3.7,<3.12; 0.18.1 Requires-Python >=3.7,<3.12; 0.19.0 Requires-Python >=3.7,<3.12; 0.19.1 Requires-Python >=3.7,<3.12; 0.19.2 Requires-Python >=3.7,<3.12; 0.19.2 Requires-Python >=3.8,<3.12; 0.19.3 Requires-Python >=3.8,<3.12; 0.19.4 Requires-Python >=3.8,<3.12; 0.19.5 Requires-Python >=3.8,<3.12; 0.20.0 Requires-Python >=3.8,<3.12; 0.20.1 Requires-Python >=3.8,<3.12; 0.21.0 Requires-Python >=3.8,<3.12; 0.21.1 Requires-Python >=3.8,<3.12; 0.22.0 Requires-Python >=3.8,<3.12; 0.22.1 Requires-Python >=3.8,<3.12; 0.23.0 Requires-Python >=3.8,<3.12; 0.23.1 Requires-Python >=3.8,<3.12; 2.5.2 Requires-Python <3.9dev,!=3.0.,!=3.1.,!=3.2.,!=3.3.,>=2.7; 8.0.10 Requires-Python >=3.7,<=3.11; 8.0.11 Requires-Python >=3.7,<=3.11; 8.0.12 Requires-Python >=3.7,<=3.11; 8.0.13 Requires-Python >=3.7,<=3.11; 8.0.14 Requires-Python >=3.7,<=3.11; 8.0.15 Requires-Python >=3.7,<=3.11; 8.0.16 Requires-Python >=3.7,<=3.11; 8.0.17 Requires-Python >=3.7,<=3.11; 8.0.18 Requires-Python >=3.7,<=3.11; 8.0.19 Requires-Python >=3.7,<=3.11; 8.0.20 Requires-Python >=3.7,<=3.11; 8.0.21 Requires-Python >=3.7,<=3.11; 8.0.22 Requires-Python >=3.7,<=3.11; 8.0.23 Requires-Python >=3.7,<=3.11; 8.0.24 Requires-Python >=3.7,<=3.11; 8.0.25 Requires-Python >=3.7,<=3.11; 8.0.26 Requires-Python >=3.7,<=3.11; 8.0.27 Requires-Python >=3.7,<=3.11; 8.0.28 Requires-Python >=3.7,<=3.11; 8.0.29 Requires-Python >=3.7,<=3.11; 8.0.30 Requires-Python >=3.7,<=3.11; 8.0.31 Requires-Python >=3.7,<=3.11; 8.0.32 Requires-Python >=3.7,<=3.11; 8.0.33 Requires-Python >=3.7,<=3.11; 8.0.34 Requires-Python >=3.7,<=3.11; 8.0.7 Requires-Python >=3.7,<=3.11; 8.0.8 Requires-Python >=3.7,<=3.11; 8.0.9 Requires-Python >=3.7,<=3.11
ERROR: Could not find a version that satisfies the requirement umap==0.1.1 (from versions: none)
ERROR: No matching distribution found for umap==0.1.1
Thanks for your reply. The error info is listed above.
Whether the python version is 3.11 or 3.12, I have encountered the problem about umap==0.1.1.
YoungDubbyDu commentedon Feb 27, 2026
Thanks for sharing the error details.
We just re-tested the installation in a clean environment (Python 3.12), and it installs successfully on our side.
If
umap==0.1.1cannot be resolved in your environment, you can safely comment out or remove that line fromrequirements_domain.txt, as it is not required for the main workflow.
Let us know if the issue persists.
Respect metric direction in fetch_child_memory