The tutorial on the site creates an app named polls. It's using django 1.9, so in the INSTALLED_APPS it is:
polls.apps.PollsConfig
I'm watching a tutorial he names the app newsletter and in INSTALLED_APPS he has
newsletter
he's using 1.8, though. I am using 1.9. I've watched other tutorials and they also just add a name without dots in the syntax as he does. I realize things may be different, that's understood. To be clear if I named my app dogs,. in the installed apps it would be named like this
dogs.apps.DogsConfig
or if it was tree it would be
tree.apps.TreeConfig
Is that how the naming convention goes? also I would assume things would get shorter in newer versions and more convenient. so to go from just adding
newsletter,
to having to type out
polls.apps.PollsConfig
seems weird to me. But I'm new so I maybe missing something. Any and all advice is welcome
Modules should have short, all-lowercase names. Underscores can be used in the module name if it improves readability. Python packages should also have short, all-lowercase names, although the use of underscores is discouraged. So, 1 and 3 are both valid, but 3 would be the recommended approach.
In your settings.py file, you will find INSTALLED_APPS. Apps listed in INSTALLED_APPS are provided by Django for the developer's comfort.
AppConfig subclasses may be defined anywhere. The apps.py convention merely allows Django to load them automatically when INSTALLED_APPS contains the path to an application module rather than the path to a configuration class.
That is the Application Configuration feature, new to Django 1.7.
Basically, now you can list in INSTALLED_APPS
either the module that contains the application or a class that derives from django.apps.AppConfig
and defines the behavior of the application.
This feature provides several advantages:
Application modules can define the special module variable default_app_config
to specify the name of their AppConfig
, so that they can use the new features without having to specify the full name of that class in INSTALLED_APPS
. But this is a backwards compatibility feature and new applications are recommended to write the full AppConfig
name.
Anyway, most django/contrib
apps use that default_app_config
, for compatibility with old configurations. See for example the file django/contrib/messages/__init__.py
is just:
from django.contrib.messages.api import *
from django.contrib.messages.constants import *
default_app_config = 'django.contrib.messages.apps.MessagesConfig'
So, adding it up, per OP request:
INSTALLED_APPS
the typename foo.apps.FooConfig
, then that class will be used to setup the foo
app, 1.7 style (recommended).If you add in INSTALLED_APPS
the plain name foo
, then:
foo.default_app_config
this class will be used to setup the foo
app, 1.7 style. Most (all?) the standard Django apps have this variable, so that you don't need to change your INSTALLED_APPS
when you upgrade from Django-1.6 to Django-1.7.In the setup.py ,under the Installed apps just add app_name
like
INSTALLED_APPS = [
'polls', # <--- here
'django.contrib.admin',
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.messages',
'django.contrib.staticfiles',
]
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With