> 1) "response" at a StackedObjectProxy in TG2? <<<SNIP>>> > I think the "global" response leaves room for a nicer API.
Yea, I agree th > 2) I'd also like to extract a couple of methods from the "route" > method so they can be easily subclassed. The first methods that comes > to mind is "validate" , "lookup_controller" and "render". > > However, in order for Pylons' dispatcher not to "expose" them, they > need to be prefixed with an underscore. The problem with this is that > it's not obvious that those methods should/could be overrided by > subclasses since a leading underscore is a python idiom to mark a > method private. Another problem is that api docs generators will > probably ignore them when documenting the public API. > > So I'm looking for suggestions on this... some ideas: > > 1) tweak the dispatcher so it never calls those methods, even though > they're not underscore prefixed. > 2) come up with a prefix and document it, for example, _tg_validate, > _tg_lookup_controller, etc... we'll alose need to tweak the api > generator so it document's them. > 3) ???? I think most of the methods in PylonsController have the same problem. But pudge has an hack __pudge_all__ = ['_inspect_call', '__call__', '_attach_locals'] So I'd say we go with _prefixing, and deal with things as they come. If we decide to use something other than pudge, we can hack that too, and if pylons/paste/toscawidgets move too the hack will be useful to others... --Mark Ramm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
