I recommend that you don't do this. It sounds convenient now, but as your project or package matures, you will end up creating an unmaintainable mess.
The big benefit of having declaring all the routes together, is that you have a single chunk of code that maps every single route -- and lets you re-order them as needed. this can be important when trying to resolve how routes are interpreted. it also lets you consolidate the various route filtering and predicate functions in a single place. by migrating the routes declarations to be in includes, or next to view callables, it becomes ridiculously hard to figure out what all your urls are. When doing future maintenance, you (or someone else), will need to search every view file for the route declarations. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
