1 # Buildsheet autogenerated by ravenadm tool -- Do not edit.
3 NAMEBASE= python-django-appconf
7 SDESC[v11]= Django configure defaults helper class (3.11)
8 SDESC[v12]= Django configure defaults helper class (3.12)
9 HOMEPAGE= https://django-appconf.readthedocs.io/
10 CONTACT= Python_Automaton[python@ironwolf.systems]
13 SITES[main]= PYPIWHL/c0/98/1cb3d9e8b1c6d0a74539b998474796fc5c0c0888b6201e5c95ba2f7a0677
14 DISTFILE[1]= django_appconf-1.0.6-py3-none-any.whl:main
19 OPTIONS_AVAILABLE= PY311 PY312
20 OPTIONS_STANDARD= none
21 VOPTS[v11]= PY311=ON PY312=OFF
22 VOPTS[v12]= PY311=OFF PY312=ON
24 DISTNAME= django_appconf-1.0.6.dist-info
28 [PY311].RUN_DEPENDS_ON= python-Django:single:v11
29 [PY311].USES_ON= python:v11,wheel
31 [PY312].RUN_DEPENDS_ON= python-Django:single:v12
32 [PY312].USES_ON= python:v12,wheel
34 [FILE:2975:descriptions/desc.single]
38 A helper class for handling configuration defaults of packaged Django
43 This app precedes Django's own AppConfig_ classes that act as
44 "objects [to] store metadata for an application" inside Django's
45 app loading mechanism. In other words, they solve a related but
46 different use case than django-appconf and can't easily be used
47 as a replacement. The similarity in name is purely coincidental.
50 https://docs.djangoproject.com/en/stable/ref/applications/#django.apps.AppConfig
55 Say you have an app called myapp with a few defaults, which you want
56 to refer to in the app's code without repeating yourself all the time.
57 appconf provides a simple class to implement those defaults. Simply add
58 something like the following code somewhere in your app files:
60 .. code-block:: python
62 from appconf import AppConf
64 class MyAppConf(AppConf):
72 AppConf classes depend on being imported during startup of the Django
73 process. Even though there are multiple modules loaded automatically,
74 only the models modules (usually the ``models.py`` file of your
75 app) are guaranteed to be loaded at startup. Therefore it's recommended
76 to put your AppConf subclass(es) there, too.
78 The settings are initialized with the capitalized app label of where the
79 setting is located at. E.g. if your ``models.py with the AppConf class
80 is in the myapp`` package, the prefix of the settings will be MYAPP.
82 You can override the default prefix by specifying a prefix attribute of
85 .. code-block:: python
87 from appconf import AppConf
89 class AcmeAppConf(AppConf):
98 The MyAppConf class will automatically look at Django's global settings
99 to determine if you've overridden it. For example, adding this to your
101 ``settings.py would override SETTING_1 of the above MyAppConf``:
103 .. code-block:: python
105 ACME_SETTING_1 = "uno"
107 Since django-appconf completes Django's global settings with its default
109 (like "one" above), the standard ``python manage.py diffsettings`` will
111 these defaults automatically.
113 In case you want to use a different settings object instead of the default
114 ``'django.conf.settings'``, set the holder attribute of the inner
115 Meta class to a dotted import path:
117 .. code-block:: python
119 from appconf import AppConf
121 class MyAppConf(AppConf):
129 holder = 'acme.conf.settings'
131 If you ship an AppConf class with your reusable Django app, it's
132 recommended to put it in a ``conf.py file of your app package and
133 import django.conf.settings`` in it, too:
138 c3ae442fba1ff7ec830412c5184b17169a7a1e71cf0864a4c3f93cf4c98a1993 6424 django_appconf-1.0.6-py3-none-any.whl