On Thursday February 12, 2009 14:10:27 Michael Brickenstein wrote: > Hi Gustavo!
Guten tag! :) > Isn't it safe, just to raise an Exception in this case? > so either > - the user has to provide the environ > or > - the framework provides it. As far as I know, and please correct me if I'm wrong, only Pylons does not pass the environ around -- it uses its thread-local/SOP stuff instead. This is, the only framework that can pass the environ to repoze.what predicates when used as decorators is Pylons (and derivatives). Every other WSGI framework simply pass the environ to the relevant application's controller (without keeping a thread-local reference to the environ). In other words, only Pylons would be able to take advantage of that functionality. So, because it's a Pylons-specific functionality, it can't go in the core of repoze.what. repoze.what core is a minimalist package which is intended to be extended by plugins -- hence it has so much plugins in spite of being too new. Nevertheless, the repoze.what-pylons package exists to bring a better integration with repoze.what in Pylons applications (which includes TG2 apps). Everything that is Pylons-specific must go in that plugin, like this feature. By the way, we're talking about this on: http://trac.turbogears.org/ticket/2205 Cheers! -- Gustavo Narea <http://gustavonarea.net/>. Get rid of unethical constraints! Get freedomware: http://www.getgnulinux.org/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
