-
Notifications
You must be signed in to change notification settings - Fork 27.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Winodws 11 error - ModuleNotFoundError - No module named 'setuptools.command.test' - build stops #16289
Comments
Hi @smuchow1962 Just run into the same issue this morning for a completely irrelevant project. Looks like setuptools just had 72.0,0 update 3 hours ago and that's the cause of this issue. https://pypi.org/project/setuptools/#history Because we cannot "set up" setuptools' version on Pipfile directly, we made the following workaround
Hope this helps! |
I'm trying to install this as well for the first time and am seeing the same error. I tried the workaround above but got an error on the final step
|
This bug arises from changes made to As a temporary solution, I forked the project and removed the relevant code to ensure it runs smoothly. You can use the following command to install the modified version: pip install git+https://github.com/EuDs63/ffmpy.git |
thanks for the solution, I tried, but the installation also fails, what am I doing wrong?
|
Hey did you find any solution, I am facing the same issue |
you should entering venv environment and then |
The issue for me was that pip install also updated setuptools. So setting setuptools to an older version helped, but I needed to force pip to not upgrade setuptools, using the no deps flag. Example: After that I did the usual pipenv install, but your env might be different. |
I think this can be marked as an "any OS" error.. I've got the same issue on MacOs sanoma (ARM) |
setuptools.command.test was removed on 28 Jul 2024: https://setuptools.pypa.io/en/stable/history.html#v72-0-0pip |
Just looked at their repo here https://setuptools.pypa.io/en/stable/history.html#v72-0-0pip it looks like they have removed support for setuptools.command.test. |
Thank you so much, my friend! Everything works great! |
How did you "enter the venv environment" and where/how did you execute |
I'm very perplexed on how this issue can happen
|
@w-e-w : somehow pip automatically updated setuptools, and overwrites the version already available. That happened to me at least by just doing pip install pipenv. |
why are you using pipenv? we don't use it by default |
@w-e-w : I think it is not related to pipenv. I just think that installing a package with setuptool? dependencies will trigger the update to the newest version |
I'm using Pinokio and getting the same error as above. |
from stable-diffusion-webui/ type source venv/bin/activate |
another dev was able to reproduce the issue but I'm still not able to reproduce it on mine I have no idea a very strange feeling |
If it helps?
First Error thrown at me: Second Error: stderr: error: subprocess-exited-with-error Getting requirements to build wheel did not run successfully. [17 lines of output] |
@flight505 sorry to bother you.
|
You need to be in the CMD window inside that /venv/Scripts folder, then type "activate" ![]() |
@LunaticBlue378
Tip: Open the folder in file explorer and just type cmd in the folder path-bar to open cmd in the current folder |
Not sure what happened, but everything magically began to work again! |
I was fighting this issue yesterday as well... I found that if I do a fresh ie. Old version of |
@MarcusNyne |
@Haoming02, thank you for bringing this to my attention. I was camping last week but am back now and investigating the issue. The line you are commenting out is from one of my commits. I was unable to reproduce the problem locally. I tried:
Given that this behavior is not reproducible, I wonder if the upgraded setuptools pre-dates the pip upgrade. Can you do a pip list in your global environment and see if it has the newer setuptools? Can you reproduce my steps?
Please let me know if you are able to reproduce this. I would be very interested, either way. Thank you! |
I did a Then I did a clean TL;DR
|
Welp, I cannot repro it myself now either... |
@Haoming02 , thank you for your quick response! Perhaps for selfish reasons, I have been focusing on understanding if the pip upgrade was the source of the problem. I am a new contributor and would feel terrible if a code change I introduced created problems for the community. Given that this is difficult to reproduce, I think its inconclusive when considering the impact of the upgrade code change on this problem. In other words, it is possible that the problem with the new version of setuptools would have been a problem even under pip 22. I am only speculating. It is possible that the version of setuptools that was installed was a result of virtual environment creation, and not the pip upgrade. I really have no idea. Do you have any suspicions or thoughts about this based on your experience? |
Checklist
What happened?
Followed the instructions for a build from a git clone in Powershell
got this error
I also tried it with the zip file installer setup. similar result
Steps to reproduce the problem
Installed python 3.10.6
Installed git
ran the instructions as listed - both for the auto installer and the git clone method
on Drive D and not drive c
Also tried it on drive C in C:\bin\sd\sd.webui
all failures
What should have happened?
The installer should have built
What browsers do you use to access the UI ?
No response
Sysinfo
THis is in the installation - haven't even gotten far enbough
Console logs
Additional information
No response
The text was updated successfully, but these errors were encountered: