Includes basic project setups of each LTS version of Django, starting with Django 2.2.
Each project has minimal adjustments to settings file, essentially using the default settings provided with the given version of Django.
Each project also has common things set up, such as a view that requires a user login to access, a view that requires a specific permissions to access, some basic API views, etc.
The goal is to be able to easily/quickly test various common properties of Django projects, across multiple Django versions.
Currently included in this project are:
| Django Version | Version Notes | Official Support End |
|---|---|---|
| Django v5.0 | Feature Release | Aug 2025 |
| Django v4.2 | LTS | April 2026 |
| Django v3.2 | LTS (End of Life) | No Longer Supported |
| Django v2.2 | LTS (End of Life) | No Longer Supported |
This project will try to always update to include LTS versions. When "feature release" versions are included, they will be updated to the next LTS version as soon as possible.
See https://www.djangoproject.com/download/#supported-versions for Django versioning and LTS details.
In each project version, there is a scripts/run_project.sh file and a scripts/run_pytests.sh file.
Change directory into the corresponding desired django project version, create/load a virtual environment, then run the corresponding desired script.
Each project has logic to automatically create a handful of user models for testing purposes:
- Super User:
- Username:
test_superuser - Email:
test_superuser@example.com - Permissions: is_active, is_superuser
- Username:
- Admin User:
- Username:
test_admin - Email:
test_superuser@example.com - Permissions: is_active, is_staff
- Username:
- Standard User:
- Username:
test_inactive - Email:
test_superuser@example.com - Permissions: None
- Username:
- Inactive User:
- Username:
test_user - Email:
test_superuser@example.com - Permissions: is_active
- Username:
All users can have the default password temppass2.