On Fri, Apr 1, 2011 at 12:35 AM, Patryk Zawadzki <pat...@pld-linux.org>wrote:
> Hi group, > > Currently Django has its own concept of namespacing (apps) and mostly > ignores Python modules. I'd like to propose using Python paths > wherever we can instead of apps. This would solve a lot of problems > with conflicting submodule names that plague maintainers of reusable > apps and frameworks. Currently if you try to provide a base > frobnicator model and you choose to do so in > "fooframework.frobnicator.models", you pretty much forbid the users > from putting derived classes in a local module named > "frobnicator.models". Bad things happen when two apps start to provide > "frobnication_tags". > I propose the following: > * make the internal model handling operate on full paths to the > classes, rather than just the app names and class names > * make the DB table names use full python paths instead of just the > app name and the class name > I think it's may be interest to you to see on app-loading branch [1] developed by Arthur Koziel in GSoC2010 [2]. It improve model loading mechanism and add ability to specify model table name prefix in your app. See the tests [3] for examples. [1] http://code.djangoproject.com/browser/django/branches/soc2010/app-loading <http://code.djangoproject.com/browser/django/branches/soc2010/app-loading> [2] http://code.djangoproject.com/wiki/SummerOfCode2010 [3] http://code.djangoproject.com/browser/django/branches/soc2010/app-loading/tests/appcachetests <http://code.djangoproject.com/browser/django/branches/soc2010/app-loading/tests/appcachetests> -- Alex Kamedov skype: kamedov www: kamedov.ru -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
