# Improving using and updating Django settings.py

**URL:** <https://forum.djangoproject.com/t/improving-using-and-updating-django-settings-py/44193>\
**Category:** Show & Tell\
**Created:** [February 16, 2026, 1:13am UTC](https://forum.djangoproject.com/t/improving-using-and-updating-django-settings-py/44193 "2026-02-16T01:13:57Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![adamghill](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/adamghill/32/1820_2.png) [@adamghill](https://forum.djangoproject.com/u/adamghill)\
**Post date:** [February 16, 2026, 1:13am UTC](https://forum.djangoproject.com/t/improving-using-and-updating-django-settings-py/44193/1 "2026-02-16T01:13:57Z")

</div>

I’ve been thinking about the Django `settings.py` file a lot recently and was trying to see if there was any way to improve the developer experience of using it (for more back story: [Checking Django Settings - DEV Community](https://dev.to/adamghill/checking-django-settings-12g4) ).

So, I’ve been working on `dj-typed-settings`:

> **[GitHub - adamghill/dj-typed-settings: Check your Django settings for common issues.](https://github.com/adamghill/dj-typed-settings)**
>
> Check your Django settings for common issues.

Some of the goals, I was thinking about:

- Stay as close to “normal” Django settings.py usage as possible
- No dependencies outside of the Python standard library
- No runtime performance impact (other than the optional system check)

Let me know what you think or other improvements that could be done to help the DX of Django settings!