> IMHO I'd prefer to reveal the flexibility to users that willing to > customize url dispatch.
I don't want to hide the flexibility from them either, but I do wan to make environment.py and middleware.py as understandable as possible. I think a comment with a link to the doc on how to update your routes map is good enough. And moving some of these things into the framework and out of the template makes them more testable, more flexible between releases (we don't have to tell everybody to change their code if we change something. > How about put config/route.py back instead of import tg.defaults? I don't want people to think they need to do routes manually. But I'm not opposed to changing it back. I'm just reiterating the reasons why we made the change in the first place. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
