lllyasviel / lllyasviel/stable-diffusion-webui-forge
[BUG] Python version issues lead to runtime errors
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
When running stablediffusion, the prompt:
/content/stable-diffusion-webui-forge
Already up to date.
=============================================================================================
INCOMPATIBLE PYTHON VERSION
This program is tested with 3.10.6 Python, but you have 3.12.11.
If you encounter an error with "RuntimeError: Couldn't install torch." message,
or any other error regarding unsuccessful package (library) installation,
please downgrade (or upgrade) to the latest version of 3.10 Python
and delete current Python and "venv" folder in WebUI's directory.
You can download 3.10 Python from here: https://www.python.org/downloads/release/python-3106/
Use --skip-python-version-check to suppress this warning.
=============================================================================================
Python 3.12.11 (main, Jun 4 2025, 08:56:18) [GCC 11.4.0]
Version: f2.0.1v1.10.1-previous-669-gdfdcbab6
Then you can use stablediffusion, but when running the graph, an error will be reported after more than ten minutes.:
Environment vars changed: {'stream': False, 'inference_memory': 1024.0, 'pin_shared_memory': False}
[GPU Setting] You will use 93.22% GPU memory (14071.00 MB) to load weights, and use 6.78% GPU memory (1024.00 MB) to do matrix computation.
^C
The running program is then terminated
When I change the version to 3.10.6, an error will be reported:
ValueError: Key backend: 'module://matplotlib_inline.backend_inline' is not a valid value for backend; supported values are ['gtk3agg', 'gtk3cairo', 'gtk4agg', 'gtk4cairo', 'macosx', 'nbagg', 'notebook', 'qtagg', 'qtcairo', 'qt5agg', 'qt5cairo', 'tkagg', 'tkcairo', 'webagg', 'wx', 'wxagg', 'wxcairo', 'agg', 'cairo', 'pdf', 'pgf', 'ps', 'svg', 'template']
And when "Hires. fix" and "ADetailer" are enabled, an error will also be reported.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by reproducing the reported behavior with Python 3.10.6 and 3.12.11, then isolate the matplotlib backend error and the failures with Hires. fix and ADetailer. Done should identify the affected compatibility issue and provide a verified fix or reproduction-specific guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- matplotlib, python
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100