On Wednesday April 29, 2009 13:05:07 Jorge Vargas wrote:
> I just looked at this again and it's really interesting.
> The only reason this is a "monkey patch" is because you implemented it
> as such with the "booleanze_predicates" function
> according to the python documentation
That's the only way to do it, if you really want to do it.
> and I don't see why request.environ will have problems evaluating the
> values from third-part.
How are you going to pass the WSGI environ? That's the whole problem.
> as for the non-pylons this has something to do with the SOPs? it is my
> understanding you are evaluating the request on each call so why is
> this a problem?
Pylons' SOP would be one solution, but only for Pylons users.
This has been discussed a few times and we agreed that it shouldn't rely on
thread-locals to retrieve the WSGI environ. Here's the reason summarized by
On a side note...
Jorge, I share your concern that it's more complex to use than it should; even
I have found this quite annoying at times. But it seems impossible to get this
fixed in v1.X, given the design mostly inherited from tg.ext.repoze.who. The
good news is that it's one of the things repoze.what 2 will fix.
Gustavo Narea <xri://=Gustavo>.
| Tech blog: =Gustavo/(+blog)/tech ~ About me: =Gustavo/about |
Repoze-dev mailing list