[Zope] REQUEST not accessible

[Jens Vagelpohl]

On 13 Oct 2005, at 11:39, Jürgen Herrmann wrote:
> up to some time in them i could just write:
> tal:define="results python:here.Catalog.searchResults()"
>
> it seems this isn't working anymore, the catalog would return
> all brains instead of seraching the relevant ones... (completely
> ignoreing everything in REQUEST)
>
> instead i have to write now:
> tal:define="results python:here.Catalog.searchResults 
> (REQUEST=request)"
>
> i suspect that the catalog was able to acquire REQUEST via  
> self.REQUEST
> and this isn't working anymore. has anyone had a similar problem? i
> don't know what i have changed leading to these kinds of problems...

Apart from whether this worked previosuly or not, it is bad coding  
practice to rely on assumptions such as "it will somehow acquire the  
REQUEST". You should really change your code to explicity pass in  
REQUEST everywhere. Then you can stop worrying.

jens