On Tuesday 13 March 2007 17:51, John_Nowlan wrote:
> I and others here have been bitten by renaming controllers.
>
> I think it is a common python practice/pattern to inspect/use a 'base'
> name.
>
> In short I think the controller module must contain a controller called
> 'FooController'
So far so good. I read the "Pylons Execution Analysis" and that makes it
clear that the controller class that is searched for is FooController.
Blasphemy: if there is only one controller class per module file anyway
then why does the controller name has to be both in the filename and in
the class name? The redundancy looks like:
controllers/__init__.py
controllers/foo.py:
class FooController...
controllers/bar.py:
class BarController...
What about:
controllers/__init__.py
controllers/foo.py:
class Controller...
controllers/bar.py:
class Controller...
Or perhaps:
controllers/__init__.py:
class Foo...
class Bar...
I believe that renaming controllers is pretty common in a project. So
removing redundancy might be nice.
Christoph
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
