Deep-Live-Cam
Deep-Live-Cam copied to clipboard
pip install -r requirements.txt causing errors
I have set up my venv already.
ERROR: Exception:
Traceback (most recent call last):
File "C:\Users\frank\desktop\Deep-Live-Cam-main\myenv\Lib\site-packages\pip_internal\cli\base_command.py", line 105, in _run_wrapper
status = _inner_run()
^^^^^^^^^^^^
File "C:\Users\frank\desktop\Deep-Live-Cam-main\myenv\Lib\site-packages\pip_internal\cli\base_command.py", line 96, in _inner_run
return self.run(options, args)
^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\frank\desktop\Deep-Live-Cam-main\myenv\Lib\site-packages\pip_internal\cli\req_command.py", line 67, in wrapper
return func(self, options, args)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\frank\desktop\Deep-Live-Cam-main\myenv\Lib\site-packages\pip_internal\commands\install.py", line 379, in run
requirement_set = resolver.resolve(
^^^^^^^^^^^^^^^^^
File "C:\Users\frank\desktop\Deep-Live-Cam-main\myenv\Lib\site-packages\pip_internal\resolution\resolvelib\resolver.py", line 95, in resolve
result = self._result = resolver.resolve(
^^^^^^^^^^^^^^^^^
File "C:\Users\frank\desktop\Deep-Live-Cam-main\myenv\Lib\site-packages\pip_vendor\resolvelib\resolvers.py", line 546, in resolve
state = resolution.resolve(requirements, max_rounds=max_rounds)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\frank\desktop\Deep-Live-Cam-main\myenv\Lib\site-packages\pip_vendor\resolvelib\resolvers.py", line 397, in resolve
self._add_to_criteria(self.state.criteria, r, parent=None)
File "C:\Users\frank\desktop\Deep-Live-Cam-main\myenv\Lib\site-packages\pip_vendor\resolvelib\resolvers.py", line 173, in _add_to_criteria
if not criterion.candidates:
^^^^^^^^^^^^^^^^^^^^
File "C:\Users\frank\desktop\Deep-Live-Cam-main\myenv\Lib\site-packages\pip_vendor\resolvelib\structs.py", line 156, in bool
return bool(self._sequence)
^^^^^^^^^^^^^^^^^^^^
File "C:\Users\frank\desktop\Deep-Live-Cam-main\myenv\Lib\site-packages\pip_internal\resolution\resolvelib\found_candidates.py", line 174, in bool
return any(self)
^^^^^^^^^
File "C:\Users\frank\desktop\Deep-Live-Cam-main\myenv\Lib\site-packages\pip_internal\resolution\resolvelib\found_candidates.py", line 162, in
Try degrad them .
The error is because of the missing distutils module, it's not included in Python 3.12 by default.
Downgrade your python version to python 3.10 as recommended and it should be fixed.
Downgrade your python version to python 3.10 as recommended and it should be fixed.
It's not really a fix but a workaround. If a module is not included in newer Python versions, it shouldn't be used in the first place.
Thank you guys, all fixed
None is fixed, Python 3.12 still fails to build.
None is fixed, Python 3.12 still fails to build.
Degrade to python 3.10
We recommended Python 3.10; other versions are optional and not treated as bugs. Full support for other versions may be available later, but not currently.
We recommended Python 3.10; other versions are optional and not treated as bugs. Full support for other versions may be available later, but not currently.
If we already go "it works on my machine" approach, why not ship a docker image? It should never be a user's responsibility to figure out dependencies. Multiple times this has resulted in avoidable issues for people.
Also for every developer who uses a stable rolling release operating system, this is just annoying to deal with. At this point it would make way more sense to run the whole application inside a sandbox if you need that kind of controlled environment.
@TheJackiMonster Why don't you follow the instruction that using the Python 3.10? It's open source and being under the development time, we don't have time to cover them all. You should follow the instruction.
@TheJackiMonster Why don't you follow the instruction that using the Python 3.10? It's open source and being under the development time, we don't have time to cover them all. You should follow the instruction.
I don't have an issue with it not getting fixed immediately. I know that open-source projects have limited resources. But even if time is limited, it doesn't make sense to close issues like this without proper solution.
People will continue to have the same issue. They will continue reporting this issue, causing a lot of duplicates because nobody searches in already closed issues. It makes way more sense to simply leave the issue open and refer to it. So people have a way to find the current workaround and it can actually be tracked when a MR solves the issue.
Hi there @TheJackiMonster , the recommended is 3.10 as per readme. We're trying to resolve everything and most of it are already in the closed ticket. Other people are also trying to help. In case you have a solution aside from going to the recommended version, please feel free to push it to the experimental so we can also help others. 😊