> If the objective is to seperate the two systems why is having the URL > system know about Models more acceptable than having the Model system > know about URLs? This is most certainly a bike shed IMO. > > Alex
Because it's the URL system which is making those models available on the web, not the models making an URL system. In Grok to get an URL for a model we do: view.url(model) Which is as it should be. At my work we often work with model objects from the command-line, so having URL stuff in the models would just be cruft. More importantly, it keeps the dependencies clean. The package that contains the models only declares that it depends upon SQL Alchemy. Slip a model.url() in there, and now you've got to declare a dependency on an URL system and most likely you're going to have to pull in a whole web stack just to use those models. :( --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
