django修改app_label别名

最新推荐文章于 2024-07-08 16:20:11 发布

euangelion

最新推荐文章于 2024-07-08 16:20:11 发布

阅读量5.2k

点赞数 2

本文详细介绍了如何在Django应用中使用AppConfig子类为可插拔应用提供合适的名称，并提供了默认加载和用户自定义设置的方法。通过推荐的惯例将配置类放入应用程序的apps子模块，实现灵活的应用加载方式。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

For application authors¶

If you’re creating a pluggable app called “Rock ’n’ roll”, here’s how you would provide a proper name for the admin:

 
  # rock_n_roll/apps.py

from django.apps import AppConfig

class RockNRollConfig(AppConfig):
    name = 'rock_n_roll'
    verbose_name = "Rock ’n’ roll"

You can make your application load this AppConfig subclass by default as follows:

 
  # rock_n_roll/__init__.py

default_app_config = 'rock_n_roll.apps.RockNRollConfig'

That will cause RockNRollConfig to be used when INSTALLED_APPS just contains 'rock_n_roll'. This allows you to make use of AppConfig features without requiring your users to update their INSTALLED_APPS setting.

Of course, you can also tell your users to put 'rock_n_roll.apps.RockNRollConfig' in their INSTALLED_APPSsetting. You can even provide several different AppConfig subclasses with different behaviors and allow your users to choose one via their INSTALLED_APPS setting.

The recommended convention is to put the configuration class in a submodule of the application called apps. However, this isn’t enforced by Django.

You must include the name attribute for Django to determine which application this configuration applies to. You can define any attributes documented in the AppConfig API reference.

Note

If your code imports the application registry in an application’s __init__.py, the name apps will clash with the apps submodule. The best practice is to move that code to a submodule and import it. A workaround is to import the registry under a different name:

 
   from django.apps import apps as django_apps 
  