On Thu, Feb 19, 2009 at 12:51 PM, Jonathan Vanasco <[email protected]> wrote: > > mike- i like your concept > > my issue stems from looking at my routing file, and then thinking for > the first time that i was looking at old perl code and not python!
The Routes config syntax is not beautiful but it gets the job done. Minor improvements are possible, as in the Routes 2 proposal, but they have tradeoffs. > should i assume that because of this behavior, people should never > have more than one controller in a file? Using the standard PylonsApp, no. The controller class is calculated from the module name, and that doesn't allow for multiple controllers per file. You could put the actual controller class into the routing rule, and subclass PylonsApp to instantiate it directly rather than looking it up by name. But then you'd have to import all controllers into the routing module, which would increase startup time and memory use if some controllers are rarely used. -- Mike Orr <[email protected]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
