Changelogs » Django-app-settings

PyUp Safety actively tracks 268,345 Python packages for vulnerabilities and notifies you when to upgrade.



  - Ignore environment variables when using ``override_settings``.
  - Don't announce type annotations.


  - Read setting values from environment variables.
  - Add ``FileSetting``.
  - Fix bug causing ``NestedDictSetting`` to be always required.
  - Add support for python 3.8 and Django 3.0.
  - Drop support for python 2.7 and 3.4.
  - Drop deprecated type checkers.
  - Add type annotations.
  - Raise ``ImproperlyConfigured`` from ``Setting.check`` for all errors in a setting.
  - Move repository to
  - Clean tests.


  - Fix ``transform_default`` in ``NestedListSetting``, by stinovlas (see PR `61`_).
  .. _61:


  - Add ``CallablePathSetting`` (see issue `49`_ and PR `52`_).
  - Add ``NestedListSetting`` (see issue `50`_ and PR `53`_).
  - Rename ``NestedSetting`` to ``NestedDictSetting`` (old name is still available but deprecated).
  .. _49:
  .. _50:
  .. _52:
  .. _53:


  - Fix default values for empty arguments.


  - Deprecate setting checkers in favor of validators, similarly to Django form fields.


  - Add ``NestedSetting`` for easy management of nested settings.


  Going from alpha to beta status. Logic has been reworked.
  - An instance of a subclass of ``AppSettings`` will now dynamically get
  settings values from project settings, and cache them. This allows to use
  the instance the same way in code and tests, without performance loss. See
  issue `16`_.
  - Cache is invalidated when Django sends a ``setting_changed`` signal (i.e.
  when using ``TestCase`` or ``override_settings``). See issue `16`_.
  - Setting main class now accepts callable as default value, and two new
  parameters to keep control on its behavior: ``call_default``, which tells
  if the default value should be called (if callable) or not, and
  ``transform_default``, which tells if the default value should be transformed
  as well by the ``transform`` method. See issue `17`_.
  - Settings type checkers now have custom parameters like ``max_length``,
  ``empty`` or ``key_type``, that can be passed directly through the settings
  classes as keyword arguments. Check the documentation for more information.
  - Settings classes have been rewritten more explicitly, using class inheritance
  instead of hard-to-debug generators. Composed types like float lists or
  boolean sets have been removed in favor of more flexible list, set and tuple
  types which now accept an optional ``item_type`` parameter.
  - ``ImportedObjectSetting`` has been renamed ``ObjectSetting``, and now
  supports object paths down to arbitrary level of nesting. Before, it only
  supported object paths down to classes or functions, now you can for example
  give it the path to a constant in a class within a class, itself contained
  in a module within a package. It will work as long a the deepest module is
  importable through ``importlib.import_module`` and each object down to the
  last is obtainable through ``getattr`` method.
  Many thanks to `ziima`_ for having shared good ideas and thoughts!
  .. _16:
  .. _17:
  .. _ziima:


  - Add six dependency (now required).
  - Rename ``Int`` settings to ``Integer``, and ``Bool`` ones to ``Boolean``.
  - Remove metaclass generated getters and checkers.


  - Settings are not checked when they default to the provided default value.
  - Settings classes received better default values corresponding to their types.


  - Add ``full_name`` property to ``Setting`` class.
  - Add ``required`` parameter to ``Setting`` class (default ``False``).


  - Import settings classes in main module to simplify imports.


  - Add ``PositiveInt`` and ``PositiveFloat`` settings.
  - Add support for Django 1.11.
  - Implement basic settings classes.


  - Implement basic Setting class.
  - Pin dependencies.
  - Change distribution name to ``app-settings``.


  - Alpha release on PyPI.