Hello Graham,

When do you try to access the cherrypy.request attributes exactly? I mean at
which step of the REQUEST processing?

- Sylvain

Selon Graham Ashton <[EMAIL PROTECTED]>:

>
> I'm trying to access the cherrypy.request.params dictionary from within
> my controller, but it doesn't appear to exist. I realise that this
> dictionary is made available as **kwargs, but I wanted it available via
> a global variable so that I could write a function to handle it. I may
> be able to achieve the same result with decorators, but I'm not sure
> yet.
>
> There seems to be a lot of other potentially useful stuff available in
> the cherrypy.request object however, and I'd be interested to know how
> to get hold of it.
>
> The cherrypy docs imply that they should all be available directly, so
> I'm wondering if it's been renamed in TurboGears. When I call "print
> dir(cherrypy.request)" inside my controller all I get back is this:
>
> ['__attrname__', '__delattr__', '__doc__', '__getattr__', '__init__',
> '__module__', '__setattr__', 'purge__']
>
> Thanks,
>
> Graham
>
>




----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Reply via email to