benoitbryon/django-confit

Django settings loaders and validators, with local flavor

django-confit's Issues

non-explicit install_requires in setup.py lies

Each release of Django requires update of django-confit.
So either:

• be explicit in setup's install_requires
• or find a way to automatically support new versions of Django

Can't use django-confit with Django>=1.7, even if not using validation

Configuration loaders may be enough in some cases. They should be usable with unsupported Django versions.
Let's remove the Django<1.7 in setup.py.

Tox runs sphinx builds using sphinx-build command

Improve integration of Sphinx with Tox, using https://testrun.org/tox/latest/example/general.html#integrating-sphinx-documentation-checks

Currently, tox runs make, which is a system dependency easily available on Linux systems.
Using sphinx-build may be more elegant, since it is a dependency installed in Python environment.

Demo project registers a custom configuration schema

Document confire alternative

http://confire.readthedocs.org/

Support Django-1.9

Add Celery settings

A lot of work :/

http://celery.readthedocs.org/en/latest/configuration.html?highlight=celery_result_backend

validate_settings() emits a warning if some directives are unused

Currently, if you have some directive in settings that is not registered in a schema, then it is not part of cleaned settings, silently.
The most common issue with that is a schema is missing. As an example, you just enabled some third-party app and related configuration => the configuration is not in cleaned settings and it is hard to figure out why.
=> when some configuration directives are in raw settings but not in cleaned settings, tell the user!

Code repository contains a demo project

Let's illustrate usage with a demo project inside code repository.
Could be useful too to perform tests on a real life example.

Implement schemas of some third-party applications

Django-confit's vision is "third-party projects declare their own configuration schema".
But right now, django-confit is just a proof of concept and third-party projects do not declare their own schema in a way compatible with django-confit. That is a fact.
So developers who want to try django-confit currently have to write those schemas.
=> Collect/write and share some popular schemas in django-confit, so that it is quite easy to use. "Some schemas" means 1 is enough, 3 is good, 5 is not a goal.

Support django-pimpmytheme settings

See https://pypi.python.org/pypi/django-pimpmytheme

Missing CSRF_COOKIE_HTTPONLY setting

It seems that two settings are not declared:

• SESSION_COOKIE_HTTPONLY (https://docs.djangoproject.com/en/dev/ref/settings/#session-cookie-httponly) Django 1.7+
• CSRF_COOKIE_HTTPONLY (https://docs.djangoproject.com/en/dev/ref/settings/#csrf-cookie-httponly)

Drop support of Django-1.5

Support Django versions from 1.5 to 1.5.8 and from 1.6 to 1.6.5

Implementation of such a feature may include changes that make it easier to manage different versions.

Support Django-1.8

Drop support of Django-1.6

DjangoSettingsSchema.TEMPLATE_LOADERS does not accept tuples

TEMPLATE_LOADERS should permits the following value:

TEMPLATE_LOADERS = (                                                               
    'django.template.loaders.cached.Loader', (                                     
        'django.template.loaders.filesystem.Loader',                                                                                                                                                                                        
        'django.template.loaders.app_directories.Loader',                          
    ),                                                                             
)

colander.Sequence() do not permit to allow different kinds of items, but colander.List() is may be too weak to validate something good.

Drop support of Python-3.3

Django 1.8 dropped support of Python 3.2 and 3.3
See also https://code.djangoproject.com/ticket/25868

Support Django 1.9.6

Document confiture alternative

See https://pypi.python.org/pypi/confiture => document similarities/differences in docs/about/alternatives

Latest Sphinx deprecates "default" theme

Warning, treated as error:
WARNING: 'default' html theme has been renamed to 'classic'. Please change your html_theme setting either to the new 'alabaster' default theme, or to 'classic' to keep using the old default.

At least 2 options to fix it:

• change Sphinx configuration file
• freeze "old" Sphinx version

AttributeError: 'module' object has no attribute 'ADMIN_FOR'

With Django 1.9:

File "/usr/local/lib/python2.7/site-packages/django_confit/schemas/django.py", line 32, in DjangoBaseConfigurationSchema
    missing=global_settings.ADMIN_FOR,
AttributeError: 'module' object has no attribute 'ADMIN_FOR'

Support Django 1.7

Declare schema for Django 1.7

load_file("path/to/file.py") loads Python module

At the moment, load_file() detects json and yaml based on the extension. Could support Python files too!

Drop support of Django-1.7

Support Django 1.6

Declare schema for Django 1.6.

Upgrade Django support to versions 1.5.12 and 1.6.11