> On Jul 8, 7:25 am, Kenneth Gonsalves <[email protected]> wrote: >> >> any reason why get_model() in django.db.models is not documented? Or is it >> just that I cannot find it?
No - it isn't documented. The app/model loading APIs are in the same category as _meta -- API that is fairly important for meta-programming, but that has never been formally stabilized. The simple reason for this is that nobody has pressed the issue. However, they could be considered psuedo-stable -- they're sufficiently entrenched that we're not going to change them without a very good reason. That said -- there is a GSoC project that is currently looking at the application loading process, and one of the upshots from that may be some changes to the get_model family of APIs. Hopefully those changes won't be too widespread, or at the very least, the old interface will remain (with warnings) for transition purposes. On Thu, Jul 8, 2010 at 5:29 PM, [email protected] <[email protected]> wrote: > I've never found any documentation. It's pretty useful if you're > having import issues. I'm not entirely sure what sort of import issues you're referring to here, but get_models() isn't intended as a solution for import issues. If you're having import issues, that should generally be considered a bug, either in your own code, or possibly in Django itself. get_model() et al are intended utilities for metaprogramming -- for example, if you want to build an interface that can knows about other models in the project, get_model() and friends are the tools you use. Yours, Russ Magee %-) -- 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.
