It would not be a "hard link". Do you know the definition of "dependency graph", and do you know anything about Django's internals or about how Django already allows you to connect models' foreign keys this way? It would be simply "get me the model 'MyModel' from the app 'my_app'". The app could easily be moved around, and no extra imports would be used in the process (see models.get_models()). This gives you the ability to move the app around easily. The real benefit in my oppinion would be the ability to connect signals for models from app A inside of app B without having to worry about import order or errors, due to some crisscross in app A's dependency graph.
On May 12, 4:24 am, Dougal Matthews <[email protected]> wrote: > On 9 May 2012 22:14, Yo-Yo Ma <[email protected]> wrote: > > > This would allow for better decoupling of code, as well as a far > > cleaner dependency graph. > > The dependancy will still be there, the string containing the dotted path > would be a hard link. However, this will be hidden and a less obvious > dependancy than a normal Python import. > > So, I'd be -1 as I don't see the advantage of this and rather it just adds > further complexity. -- 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.
