"Project" Naming Conventions

Using Django Getting Started
13

Sorry for bumping up an old thread but why not use the THUNDER scheme. THUNDER stands for THree UNDERscores.

md yourprojectdir
cd yourprojectdir

# create your pipenv environment of whatever you use

django-admin startproject ___ .

For each real project, naming in Django the project as “___” has the following benefits:

  1. It’s a valid python variable/dir name.
  2. standardizes naming convention for a directory that’s always present in a Django project
  3. No trouble when jumping between projects, all have settings.py/etc in the same dir
  4. No name collision with possible apps since there is no name
  5. Simple & short
  6. No confusion when reading, no mental translation or name association needed

    from ___.settings import ROOT_URLCONF

    from ___.urls import *

  7. Easily floats-to-top or sinks-to-bottom in dir listings
  8. In VSCode floats to top, even above your (dot)xxx dirs, clearly separating your main config files from your application structure.

Any thoughts?

Best regards
Alex