Replies: 1 comment
-
|
I would like this as well. it would be maybe a little simpler that what might exist as an alternative. But looking at the tools already available. If you add to the blacklist the versions that you don't want. Then maybe it can prevent manager from constantly installing the libraries that break your install. I have not tried this solution yet. my solution, such as it is was to use a bat to install requirements to downgrade. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Custom nodes often have something like numpy in requirements.txt.
This means that the latest version is installed during installation, e.g., numpy 2.3. This causes problems because numba only runs with numpy 2.1. This could be prevented by creating a contraints.txt file and writing numpy==2.1.0 in it, for example, so that custom nodes do not install any other version.
My idea would be to add a field in the manager where you can specify the path to a contraints.txt file. If the field is not empty and the constraints.txt file is found, the manager should take this into account when restarting.
Something like
if constraints_path:
([‘install’, ‘-r’, requirements_path] ‘--constraint’, constraints_path)
else:
([‘install’, ‘-r’, requirements_path])
Or is it the same like this:
Configurable pip auto fix: <USER_DIRECTORY>/default/ComfyUI-Manager/pip_auto_fix.list
Beta Was this translation helpful? Give feedback.
All reactions