Automatic registration of co-installed 3rd party library types about glom HOT 4 OPEN

If glom is in INSTALLED_APPS, then it will import the app in glom.default_app_config, for example with glom.default_app_config = 'glom.django.app.AppConfig' then this allows AppConfig to do the registration in ready().

https://docs.djangoproject.com/en/2.0/ref/applications/

from glom.

@jpic that's some good detailed info! Interestingly that would involve making glom into a django app, even if not directly depending on django as an installation requirement. Am I understanding that correctly? Definitely worth a think, even if it doesn't answer the question for SQLAlchemy and other libraries with interesting types.

from glom.

Well, there will be a conflict if another library that's not compatible with Django decides to use glom.default_app_config, load the module it contains as a string, and expect anything else than a Django App, otherwise, everything will be fine.
Otherwise, we could have a django app in glom/django_glom, then the user can add glom.django_glom to INSTALLED_APPS and benefit from auto registration with the App class, that could also autodiscover glom.py files from INSTALLED_APPS like Django already does for the admin or models.
Otherwise, you can move glom/ to src/glom and change the setup script to it install all modules from src/, then it will install src/glom_django, src/glom_sqlalchemy, etc ... you can see examples in yourlabs/django-autocomplete-light or yourlabs/crudlfap, their setup.py install all modules in src/ subdirectory which is great to keep control on depencency coupling.
But before SQLAlchemy I'd like to check if glom can support also Django Forms or WTForms library 😂
Let me know if you want me to propose a patch of one of the things i'm talking about ;)

from glom.

Forgot to show example django app auto discovery for registration: https://github.com/yourlabs/crudlfap/blob/master/src/crudlfap/apps.py

from glom.