On Apr 9, 2:09 am, Nick Sandford <[email protected]> wrote: > It's a great place to start, and gives a good idea about where to look for > problems. I'm not sure about get_installed_app_paths, rather than modifying > settings.INSTALLED_APPS to contain a tuple of strings pointing to all > application paths. If we end up using get_installed_app_paths it would break > all of those using for app in settings.INSTALLED_APPS in third party code.
You're right: get_installed_app_paths needs to be replaced with e.g. get_installed_apps() to get the app instances, while INSTALLED_APPS remains a list of path strings. That will avoid backward compatibility problems with 3rd-party code. > You've taken the route of assuming applications won't know their models > until runtime, I've expected that people explicitly assign models to apps. > Not exactly, it was more a case of keeping the changes as small as possible, at the time of the original patch. It's certainly better to have models explicitly associated with apps - it would make some things easier, especially in a multi-db setup. Regards, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en.
