On Sun, 2009-05-03 at 10:01 -0700, Rick Wagner wrote: > > > Thank you for the explanation. I think this trick is not in the > > > Documentation yet > > > > That's because it's pretty basic Python knowledge. I'm sure I've read > > on this list that basic Python knowledge isn't supposed to be > > documented in Django as it's already part of the official Python > > documentation (http://docs.python.org/tutorial/modules.html#packages) > > Most of it is a knowledge of Python, but the need for adding things > like app_label is not obvious. Once I'm clear on how Django's model > framework introspects the Python classes it finds in an application, > I'll try to write up an internally consistent addition to the docs.
The preferred solution is to fix the problem so that app_label doesn't have to be specified. There's already a ticket open that, I'm sure, since people keep saying "I'll work on it". It's probably not even that hard to get right -- although all attempts to do so to date have only fixed the basic cases and not the general situation (arbitrary levels of imports). Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
