mirror of
https://github.com/RVC-Project/Retrieval-based-Voice-Conversion-WebUI.git
synced 2026-11-05 00:27:30 +00:00
[GH-ISSUE #1053] requirements-dml.txt is incompatible with any and all Python versions #691
Labels
No labels
AMD/Intel
bug
bug
bug
colab
dependencies
documentation
duplicate
enhancement
following up
good first issue
help wanted
invalid
question
stale
stale
stale
todo list
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
RVC-Project/Retrieval-based-Voice-Conversion-WebUI#691
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @NatoBoram on GitHub (Aug 19, 2023).
Original GitHub issue: https://github.com/RVC-Project/Retrieval-based-Voice-Conversion-WebUI/issues/1053
In Preparing the environment, it states this:
However, if I try to install dependencies (
pip install -r requirements-dml.txt) with3.8.17, I get this error:This leads me to believe that it works on 3.9-3.12, but not on 3.8.
Now if I try the latest of this range (3.11.4), I get this error:
The range of possible versions was diminished to 3.9-3.10.
Now if I try the latest of this range (3.10.12), I get these errors:
If I try with the last version remaining (3.9.17), I get this:
So now it wants 3.7-3.8. But we already determined that 3.9-3.12 was required earlier.
In short, it's physically impossible to install dependencies on any and all versions of Python currently in existence.
@NatoBoram commented on GitHub (Aug 28, 2023):
One workaround is to
xargseach requirement intopip install.Works with Python 3.10.13.
@emyfops commented on GitHub (Jul 31, 2024):
For windows users, you can achieve a similar result with powershell using
Get-Content requirements-dml.txt | ForEach-Object { pip install $_ }@RVC-Boss commented on GitHub (Jul 20, 2026):
You can update the code to the latest
mainbranch, where this install issue has already been resolved.