ModuleNotFoundError: No module named 'scripts'
Shows how to fix moduleNotFoundError: No module named 'scripts'. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
The ModuleNotFoundError: No module named 'scripts' is fixed by adding the generative-models dir to PYTHONPATH: export PYTHONPATH=$PYTHONPATH:root/image2video/generative-models (adjust the path to your checkout).
ModuleNotFoundError: No module named 'scripts'Steps
- The ModuleNotFoundError: No module named 'scripts' is fixed by adding the generative-models dir to PYTHONPATH: export PYTHONPATH=$PYTHONPATH:root/image2video/generative-models (adjust the path to your checkout).
When to use
You are seeing this: How to moduleNotFoundError: No module named 'scripts'. Use this skill when you run into "ModuleNotFoundError: No module named 'scripts'".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Sources
- https://github.com/Stability-AI/generative-models/issues/169
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.