django-split-settings
Organize Django settings into multiple files and directories. Easily override and modify settings. Use wildcards and optional settings files.
Decision gist · record as of 2026-08-14
Yes. The package is stable (Production/Stable status, no known vulnerabilities), has zero dependencies, and solves a real pain point in Django configuration management. Dormant maintenance is a minor concern—the package is simple and unlikely to need frequent updates—but verify compatibility with your specific Django and Python versions before adopting.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.9+ and Django 4.2, 5.0, or 5.1; BASE_DIR path calculation changes when settings becomes a module rather than a file.
- Low friction: no runtime dependencies, pure Python wheel.
- Dormant maintenance (770 days since last release) but stable and production-ready; officially supports Django 4.2, 5.0, 5.1 and Python 3.9–3.12.
License · maintenance · safety
BSD-2-Clause (permissive) — BSD-2-Clause permissive license; no restrictions on use, modification, or distribution in commercial or private projects.
last release 2024-07-05 (770 days)
0 known vulnerabilities (OSV.dev, 2026-08-14) · 363,342 downloads/mo, #7,222 on PyPI
Alternatives
Verify before relying
pip install django-split-settings
# In settings/__init__.py or settings.py:
from django_split_settings import optional, include
include(
'components/base.py',
'components/database.py',
optional('local_settings.py')
)- Whether dormant status (no commits in 770 days) affects compatibility with future Django or Python releases.
- Performance impact of wildcard includes on large numbers of settings files.
- Exact import path and API surface of the package's public interface.
What it is and what it does
django-split-settings lets you break a monolithic Django settings.py into separate, composable files organized by concern—database config, installed apps, logging, environment-specific overrides—and include them in order. Each included file has access to the settings namespace built by previous files, so later files can import and modify earlier settings. You can use glob wildcards to include groups of files, mark files as optional (included only if they exist), and organize settings hierarchically in subdirectories.
The package is a pure-Python utility with no dependencies, making it lightweight to add to any Django project. It's useful for teams managing multiple environments (dev, staging, production), for large projects where settings have grown unwieldy, or for monorepos where different services need different configurations. The main gotcha is that BASE_DIR path calculations need adjustment when settings becomes a module instead of a single file.
Use it for
- Separate database, cache, logging, and app-specific settings into individual files for clarity and reuse.
- Manage environment-specific overrides without duplicating base configuration across dev, staging, and production.
- Organize settings by feature or app in a large Django project to reduce merge conflicts and improve maintainability.
- Use wildcards to auto-include all settings from a directory without manually listing each file.
- Mark optional settings files so local developer overrides don't break CI/CD or production deployments.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes.
The package is stable (Production/Stable status, no known vulnerabilities), has zero dependencies, and solves a real pain point in Django configuration management. Dormant maintenance is a minor concern—the package is simple and unlikely to need frequent updates—but verify compatibility with your specific Django and Python versions before adopting.
Install
django-split-settings on PyPI
Before you install
Low friction: no runtime dependencies, pure Python wheel. Dormant maintenance (770 days since last release) but stable and production-ready; officially supports Django 4.2, 5.0, 5.1 and Python 3.9–3.12.
Requires Python 3.9+ and Django 4.2, 5.0, or 5.1; BASE_DIR path calculation changes when settings becomes a module rather than a file.
License in practice
BSD-2-Clause permissive license; no restrictions on use, modification, or distribution in commercial or private projects.
Quickstart
pip install django-split-settings
# In settings/__init__.py or settings.py:
from django_split_settings import optional, include
include(
'components/base.py',
'components/database.py',
optional('local_settings.py')
)Verify before relying
- Whether dormant status (no commits in 770 days) affects compatibility with future Django or Python releases.
- Performance impact of wildcard includes on large numbers of settings files.
- Exact import path and API surface of the package's public interface.
Package facts
| License | BSD-2-Clause permissive |
| Python support | Supports the current Python release <4.0,>=3.9 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | None |
| Maintenance | Dormant 770 days since the last release |
| First released | |
| Downloads | 363,342 / month, #7,222 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Development Status :: 5 - Production/StableEnvironment :: Web EnvironmentFramework :: DjangoFramework :: Django :: 3.2Framework :: Django :: 4.0Framework :: Django :: 4.1Framework :: Django :: 4.2Framework :: Django :: 5.0Intended Audience :: DevelopersLicense :: OSI Approved :: BSD LicenseOperating System :: OS IndependentProgramming Language :: Python :: 3Programming Language :: Python :: 3.10Programming Language :: Python :: 3.11Programming Language :: Python :: 3.12Programming Language :: Python :: 3.9Topic :: Internet :: WWW/HTTPTopic :: Internet :: WWW/HTTP :: Dynamic ContentTopic :: Software Development :: Libraries :: Python Modules |
Evidence: django_split_settings-1.3.2-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “django settings organization”
- django-split-settingsSplits Django settings across multiple files and directories with…
- django-dynamic-preferencesStores and retrieves application settings dynamically in a Django…
- django-auth-adfsIntegrates Django applications with Microsoft ADFS and Azure AD for…
Give your agent the search over MCP, or paste the wish link into any chat.
More Python Modules packages
Converts domain names between Unicode and ASCII-compatible encoding (Punycode) according to IDNA 2008 and Unicode Technical Standard 46, with security validation and broader script coverage than the standard library.
Install it if you work with internationalized domain names, need to validate domains, or use HTTP clients that depend on it transitively.
Setuptools is a Python build backend and package management tool that handles building, distributing, and installing Python packages, including support for C/C++ extension modules.
PyYAML parses and emits YAML 1.1 data format, enabling serialization and deserialization of configuration files and Python objects to and from human-readable YAML text.
Pydantic validates Python data structures against type hints, coercing and checking input at runtime to ensure it matches a declared schema.
Provides reusable metadata objects for use with PEP-593 `typing.Annotated` to express common constraints like bounds, collection sizes, and predicates on types.
Install it if you use or build libraries that need to express type constraints in a standardized, inspectable way—or if you want to annotate your own types with…
Provides runtime tools to inspect and introspect Python type annotations, enabling programmatic examination of type hints at execution time.
See also django-environ · django-configurations · django-settings-export · django-fiber · django-dynamic-preferences · python-decouple · django-pipeline · django-constance · django-dotenv · django-decorator-include