重新迁移，寻找更干净的板块。

这可以毫不痛苦地做，如果其他应用程序没有外键模型从应用程序被重命名。检查并确保他们的迁移文件没有列出任何来自此迁移的迁移。

Backup your database. Dump all tables with a) data + schema for possible circular dependencies, and b) just data for reloading. Run your tests. Check all code into VCS. Delete the database tables of the app to be renamed. Delete the permissions: delete from auth_permission where content_type_id in (select id from django_content_type where app_label = '<OldAppName>') Delete content types: delete from django_content_type where app_label = '<OldAppName>' Rename the folder of the app. Change any references to your app in their dependencies, i.e. the app's views.py, urls.py , 'manage.py' , and settings.py files. Delete migrations: delete from django_migrations where app = '<OldAppName>' If your models.py 's Meta Class has app_name listed, make sure to rename that too (mentioned by @will). If you've namespaced your static or templates folders inside your app, you'll also need to rename those. For example, rename old_app/static/old_app to new_app/static/new_app. If you defined app config in apps.py; rename those, and rename their references in settings.INSTALLED_APPS Delete migration files. Re-make migrations, and migrate. Load your table data from backups.

在很多情况下，我认为@allcaps的答案效果很好。

然而，有时确实需要重命名应用程序，例如提高代码可读性或防止混淆。

大多数其他答案都涉及手工数据库操作或对现有迁移进行修补，我不太喜欢这种方法。

作为一种替代方法，我喜欢用想要的名称创建一个新的应用程序，复制所有内容，确保它可以工作，然后删除原来的应用程序:

Start a new app with the desired name, and copy all code from the original app into that. Make sure you fix the namespaced stuff, in the newly copied code, to match the new app name. makemigrations and migrate. Note: if the app has a lot of foreign keys, there will likely be issues with clashing reverse accessors when trying to run the initial migration for the copied app. You have to rename the related_name accessor (or add new ones) on the old app to resolve the clashes. Create a data migration that copies the relevant data from the original app's tables into the new app's tables, and migrate again.

此时，一切仍然正常，因为原始应用程序及其数据仍然在原地。

现在你可以重构所有的依赖代码，所以它只使用新的应用程序。有关需要注意的例子，请参阅其他答案。 一旦你确定一切正常，你可以删除原来的应用程序。这涉及到另一种(模式)迁移。

这样做的好处是，每一步都使用正常的Django迁移机制，不需要手动操作数据库，我们可以跟踪源代码控制中的所有内容。此外，我们将保留原始应用程序及其数据，直到我们确定一切正常为止。

重新迁移，寻找更干净的板块。

这可以毫不痛苦地做，如果其他应用程序没有外键模型从应用程序被重命名。检查并确保他们的迁移文件没有列出任何来自此迁移的迁移。

Backup your database. Dump all tables with a) data + schema for possible circular dependencies, and b) just data for reloading. Run your tests. Check all code into VCS. Delete the database tables of the app to be renamed. Delete the permissions: delete from auth_permission where content_type_id in (select id from django_content_type where app_label = '<OldAppName>') Delete content types: delete from django_content_type where app_label = '<OldAppName>' Rename the folder of the app. Change any references to your app in their dependencies, i.e. the app's views.py, urls.py , 'manage.py' , and settings.py files. Delete migrations: delete from django_migrations where app = '<OldAppName>' If your models.py 's Meta Class has app_name listed, make sure to rename that too (mentioned by @will). If you've namespaced your static or templates folders inside your app, you'll also need to rename those. For example, rename old_app/static/old_app to new_app/static/new_app. If you defined app config in apps.py; rename those, and rename their references in settings.INSTALLED_APPS Delete migration files. Re-make migrations, and migrate. Load your table data from backups.

如果你正在使用PyCharm并且项目在重命名后停止工作:

编辑运行/调试配置并更改环境变量DJANGO_SETTINGS_MODULE，因为它包含了您的项目名称。 进入Settings / Languages & Frameworks / Django，更新Settings文件的位置。

Django 1.7新增了一个应用注册表，用于存储配置并提供自省功能。这个机制让你改变几个应用程序的属性。

我想说的主要观点是，重命名应用并不总是必要的:通过应用配置，可以解决冲突的应用。但如果你的应用需要友好的命名，这也是一种方法。

例如，我想把我的民意调查应用程序命名为“用户反馈”。它是这样的:

在polls目录下创建一个apps.py文件:

from django.apps import AppConfig

class PollsConfig(AppConfig):
    name = 'polls'
    verbose_name = "Feedback from users"

在polls/__init__.py中添加默认应用配置:

default_app_config = 'polls.apps.PollsConfig'

更多应用配置请访问:https://docs.djangoproject.com/en/1.7/ref/applications/

我的简单替代方案避免了手工数据库操作(类似于https://stackoverflow.com/a/64133141/1608851)，在CI/CD中工作得很好，并且是可逆的。

在“旧”应用程序中创建一个空迁移，重命名表、内容类型和迁移记录。包括反向迁移。 例子:

from django.db import migrations

sql = """
ALTER TABLE oldapp_examplemodel RENAME TO newapp_examplemodel;
UPDATE django_migrations SET app ='newapp' WHERE app ='oldapp';
UPDATE django_content_type SET app_label ='newapp' WHERE app_label ='oldapp';
"""

reverse_sql = """
ALTER TABLE newapp_examplemodel RENAME TO oldapp_examplemodel;
UPDATE django_migrations SET app ='oldapp' WHERE app ='newapp';
UPDATE django_content_type SET app_label ='oldapp' WHERE app_label ='newapp';
"""


class Migration(migrations.Migration):

    dependencies = [
        ('oldapp', '0001_initial'),
    ]

    operations = [
        migrations.RunSQL(sql, reverse_sql)
    ]

将模型表名设置为new_app。 例子:

class ExampleModel(models.Model):

    # normal column definitions...

    class Meta:
        db_table = "newapp_examplemodel"  # add this line to the meta class

提交、测试和部署上述更改。 删除步骤1中创建的迁移。 重命名/移动旧应用程序并修复所有引用(参见https://stackoverflow.com/a/8408131/1608851了解更多详细信息)，包括迁移中的引用。 从模型元类中删除db_table覆盖。 提交、测试和部署。

注:

The django_migrations table will retain a row with the old app, because that row is added after our new migration was run, but before it was registered under the new app name. It should be okay to leave that as is. Deleting the migration is due to the above point, but also to prevent future issues when reverse migrating, but also because Reversing this app rename requires checking out / deploying the commit from step 3, then reversing our migration, then checking out / deploying the commit before that