Hi All, I'm Javed and I'm currently pursuing a part-time masters in Software Systems. I have been involved with django for the better part of the last few years and I love the community and ecosystem! In my spare time I try to pay back by contributing to django and supporting projects. I love the idea of decoupling django and being able to install and use only the forms or the ORM.
To try and understand the problem better I've written about the current dependencies within django: http://tuxcanfly.me/visualizing-django-component-dependencies.html I think django.conf is the most coupled module since it's virtually required everywhere to access settings. Similarly a lot of modules are coupled to django.apps to access the apps. This is probably because of django's assumption about the context of execution i.e. within a project created by startproject. Other dependencies are more complex will require more analysis. I'll try to find out more and come up with a draft for the proposal soon. If anyone has suggestions or if I'm not on the right track, please let me know. Thanks, Javed -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/eb4149ea-bec4-4345-a03e-c5a96e9a4ed7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
