Failed to download and build `visdom==0.1.8.9

[jacksphere-logger]

so apperently im trying to set up the real time voice cloning tool, i followed the set up steps " Running the toolbox '' which are 3 steps i did

i asked chatgpt and it told me that something is outdated in the master file i downloaded, and that there is no requirements.txt folder

this is the error: x Failed to download and build visdom==0.1.8.9
|-> Failed to resolve requirements from build-system.requires and extra-build-dependencies
|-> No solution found when resolving: setuptools>=40.8.0, pkg-resources
`-> Because pkg-resources was not found in the package registry and you require pkg-resources, we can conclude that
your requirements are unsatisfiable.

hint: visdom (v0.1.8.9) was included because real-time-voice-cloning (v0.0.0) depends on visdom
C:\Users\Anas_\Desktop\Real-Time-Voice-Cloning-master>

so what do i do to bypass that "visdom" problem ?

[Meyjoorstin]

Hi, I had almost the same error.

Context:

• Tried to run ".`\python\python.exe -m uv run --extra cuda demo_toolbox.py" (I'm using a portable python 3.11.9 from a local folder inside the cloned project Real-Time-Voice-Cloning.
• uv could't build "visdom", and I got the same error as you. Apparently it can't find "pkg-resources", aka setuptools, when trying to build "visdom".

Problem (I think):
When you run "uv run --extra cuda demo_toolbox.py", uv tries to separate your python environment with a newly created .venv (virtual environment). It then checks the listed dependencies and if everything looks ok (based on the uv configuration files in the project), it tries to build "visdom"... and fails.
That is because "visdom" uses "pkg-resources" during the building process inside your ".venv", but since it isn't listed in the required dependencies in the uv dependencies files it isn't added to your .venv. So your "pkg-resource" is inside your python env but not your .venv, and therefore invisible to the building process of "visdom".

Solution (worked for me at least):

1. Install visdom first using the python env, not the .venv: uv add visdom --no-build-isolation
2. Re-run the comand with visdom already done: uv run --extra cuda demo_toolbox.py

Well, it worked in my case, your error sounds very similar to mine, although our environments are a little different. Maybe you could even try uv add setuptools as the first step instead of uv add visdom --no-build-isolation? I haven't tested that, though.

If anyone has a better explanation, please don't hesitate to correct me. I'm pretty curious about what's actually happening here.