gestioCOF/kfet/apps.py

# -*- coding: utf-8 -*-
from django.apps import AppConfig


class KFetConfig(AppConfig):
    name = 'kfet'
    verbose_name = "Application K-Fêt"

    def ready(self):
        self.register_config()

    def register_config(self):
        import djconfig
        from .config import KFetConfigForm
        djconfig.register(KFetConfigForm)
Ajout message pour proposer connexion standard 2016-09-10 22:49:07 +02:00			`# -- coding: utf-8 --`
			`from django.apps import AppConfig`

Move KFetConfigForm to kfet.config Import in `ready` method of kfet app config of `kfet.forms` may be annoying because it starts executing `__init__` methods of fields. Causing failures if these methods does DB calls, as `ready` may be called before applying migrations. 2017-10-12 13:53:48 +02:00
Ajout message pour proposer connexion standard 2016-09-10 22:49:07 +02:00			`class KFetConfig(AppConfig):`
			`name = 'kfet'`
			`verbose_name = "Application K-Fêt"`

			`def ready(self):`
Use django-djconfig for kfet app. Old configuration(/settings), based on Settings model, system is deleted: SettingsForm, Settings. New system use `django-djconfig` module. - `kfet.config` module provides `kfet_config` to access configuration concerning kfet app. - Views, forms, models, etc now use this object to retrieve conf values. - Views no longer add config values to context, instead templates use `kfet_config` provided by a new context_processor. - Enhance list and update views of settings. - Fix: settings can directly be used without having to visit a specific page... Misc - Delete some py2/3 imports - Delete unused imports in kfet.models and kfet.views - Some PEP8 compliance 2017-04-03 20:32:16 +02:00			`self.register_config()`

			`def register_config(self):`
			`import djconfig`
Move KFetConfigForm to kfet.config Import in `ready` method of kfet app config of `kfet.forms` may be annoying because it starts executing `__init__` methods of fields. Causing failures if these methods does DB calls, as `ready` may be called before applying migrations. 2017-10-12 13:53:48 +02:00			`from .config import KFetConfigForm`
Use django-djconfig for kfet app. Old configuration(/settings), based on Settings model, system is deleted: SettingsForm, Settings. New system use `django-djconfig` module. - `kfet.config` module provides `kfet_config` to access configuration concerning kfet app. - Views, forms, models, etc now use this object to retrieve conf values. - Views no longer add config values to context, instead templates use `kfet_config` provided by a new context_processor. - Enhance list and update views of settings. - Fix: settings can directly be used without having to visit a specific page... Misc - Delete some py2/3 imports - Delete unused imports in kfet.models and kfet.views - Some PEP8 compliance 2017-04-03 20:32:16 +02:00			`djconfig.register(KFetConfigForm)`