重命名Django项目后启动WSGI服务器报错：找不到旧名称模块

It looks like the old project name omics is still being referenced somewhere in your codebase—even in places you might not have checked yet. Let's break down the most likely culprits and how to fix them:

1. First, Check Your server.py File #

You mentioned running python server.py, but didn't include its content. Even though the trace starts with importing from omics_server.wsgi, double-check server.py for any hidden references to omics—like stray imports or hardcoded environment variables. For example:

# Bad: Old project name in import
from omics.utils import some_function

2. Recursively Search All Python Files for omics Imports #

The error happens when Django tries to load your settings, which means somewhere in your codebase there's an import referencing the old omics module. Run these commands in your project root (the folder containing manage.py) to find all such references:

# Find all "from omics" imports
grep -r "from omics" . --include="*.py"

# Find all "import omics" statements
grep -r "import omics" . --include="*.py"

This will pinpoint exactly which files are still using the old project name as a module.

3. Check Environment Variables #

Sometimes the DJANGO_SETTINGS_MODULE environment variable might be set to the old project name, overriding the value in your wsgi.py and manage.py. Verify this with:

echo $DJANGO_SETTINGS_MODULE

If it outputs omics.settings, unset it with:

unset DJANGO_SETTINGS_MODULE

(Adjust this command if you're using a shell other than bash.)

4. Dig Deeper Into settings.py #

Your grep results show paths like /var/www/html/omics/—those are just URL paths and won't cause a ModuleNotFoundError. However, check the entire settings.py file for imports that reference omics, like:

# Bad: Import from old project module
from omics.secrets import SECRET_KEY

These kinds of imports will trigger the error when Django loads your settings.

5. Verify App Configurations #

If you have custom app configurations in apps.py files, make sure they don't reference the old project name. For example:

# Bad: Old project name in app config
class MyAppConfig(AppConfig):
    name = 'omics.myapp'

# Good: Updated project name (or just 'myapp' if it's a standalone app)
class MyAppConfig(AppConfig):
    name = 'omics_server.myapp'

6. Check URLs and Middleware #

Look through your main urls.py and any app-specific urls.py files for imports using omics. Also, check custom middleware or context processors listed in settings.py—these often reference project-level modules.

Once you've fixed all these references, restart your server and the error should disappear.

内容的提问来源于stack exchange，提问作者Soerendip