Django-settings-holder

What's Changed

Features

* Support import strings immutable sequences and mappings

Fixes

* Fix issue where reloading sequences or mappings of improt strings would error due to the import still existing in the default setting

---

**Full Changelog**: https://github.com/MrThearMan/django-settings-holder/compare/v0.2.1...v0.2.2

What's Changed

Features

* Adds option for wildcards in import string options, e.g. `"MY_SETTING.*"`, meaning any keys of `MY_SETTING` will be treated as import strings. Supported in nesting and byte import strings.

---

**Full Changelog**: https://github.com/MrThearMan/django-settings-holder/compare/v0.2.0...v0.2.1

What's Changed

Features

* BREAKING: Modify logic for nested import settings to allow more flexibility:
* If the setting is a list, you need to set `"MY_SETTING.0"` in the `import_strings` of the `settings_holder`
* If the setting is a dict, you need to set `"MY_SETTING.KEY_NAME"` in the `import_strings` of the `settings_holder` for each key that contains a dot import string.
* For deeper levels of nesting, you need to specify each level, e.g. `"MY_SETTING.0.KEY_NAME.0"`

* Allow caching settings via setting attributes to the holder so that `reload()` will still remove the cached value

---

**Full Changelog**: https://github.com/MrThearMan/django-settings-holder/compare/v0.1.2...v0.2.0

- Fix pytest plugin name

- Add ability to validate settings on first access
- Expose a `django_settings` fixture
- Improve documentation
- Update dependencies
- Test on django 5.0
- Drop support for python 3.8