Hello, Jorge. I think it's a good idea.
However, it's better to implement it in TurboGears itself because of the same reason why @require has been moved from repoze.what to TG: The only safe way to deal with the environment is by passing it around (instead of storing it in a global variable, for example). If it's implemented in repoze.what, then the three functions below will need to be passed the WSGI environment as an argument. On the contrary, if they are implemented in TurboGears, they could be defined so that the environment isn't passed as argument. Cheers! On Monday November 24, 2008 18:28:47 Jorge Vargas wrote: > hello Gustavo,all. > > I'll like to propose a bit of api, I'm not 100% sure if this isn't > really there but it will be nice. > > I suggest it will be added to repoze.what.authorize.py although with > the move of require to tgcore maybe it should be there. > > The methods are the following: > > current_user > current_groups > current_permissions > > they are all wrappers against the environ and identity dict but I > believe they are common enough to be there. > > What do you think? > > -- 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 -~----------~----~----~----~------~----~------~--~---
