> Thanks. Now I have a question for you. How would you do this in > Django? How does Routes differ from the Django dispatcher as a Django > person would see it? As you may know, I'm coordinating an upgrade to > Routes, so I'm curious about any feedback which may lead to its > improvement. For instance, I've heard that Django uses regular > expression syntax for routing, and that's the biggest thing Django > people miss when they use Routes. Would you say that's the case?
I used Django extensively an year ago and I really liked it. The URL dispatching system seems quite odd at first but it powerful indeed. There's an equivalent of url_for called reverse which works passing view or patterns names. Take a look at http://www.djangoproject.com/documentation/url_dispatch/ It does not require much knowledge of django to be read. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
