On Thu, Nov 20, 2008 at 5:04 AM, Gustavo Narea <[EMAIL PROTECTED]> wrote: > > Hello, > > I've tried my best to avoid making backwards incompatible changes while making > repoze.what TurboGears-independent, but now I must change something that will > break compatibility: > > The @require decorator in repoze.what.authorize must be moved into TurboGears > itself because repoze.what requires the WSGI environ when you check for > authorization and we couldn't find a reliable, framework-independent, thread- > safe way for repoze.what to get it. So it's going to be moved into TG so that > it'll pass the environ to repoze.what to check for authorization. > > The built-in predicates will be kept in repoze.what.authorize. The @require > decorator is the only thing that will be moved into TG.
will this affect the SecureController.require method ? from what I can infer you will be adding a "require" function somewhere in tgcore that will get the environ dict and call an equivalent "require" function at repoze.what > > I'll apply the changes in the trunk this evening. > > 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 -~----------~----~----~----~------~----~------~--~---
