On Tue, Apr 28, 2009 at 10:22 AM, Gael Pasgrimaud <[email protected]> wrote: > > On Tue, Apr 28, 2009 at 12:01 AM, Mike Orr <[email protected]> wrote: >> >> >> It works, but that's a pain if you need to put your Pylons >> authorization system around it. > > It's not a real pain if you use repoze.who/what
Yes, but some people have existing auth code (and logging code) which is working and would be too much work to port to repoze.who. Ben wrote: > I'd be curious to look over Jonathan's approach a bit more, if a 'standard' > definition for how the controllers should be pulled in, and how to extend the > template search paths properly could be reached, that would probably be the > simplest scheme that retains the separateness of a package for maintaining > versions, while still being easy enough to customize. The most difficult problem seems to be controllers, and the 'controller_scan' argument in Routes which seems useless. (We had to hardcode the controllers in our GUI BILS app because of some incompatibility with py2exe.) Several people have asked how to have controllers in various packages and then pull in a selection of them. The simplest method is stub modules in the controllers directory that import the actual controllers. But maybe we can find something more flexible. -- 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 -~----------~----~----~----~------~----~------~--~---
