Hello, everybody.
I'm working to turn tgext.authorization into a TG-independent, WSGI
authorization framework (still based on repoze.who) in the Repoze project
using repoze.what as its new name, so that more people could take advantage of
this software.
This means that, once again, we'll have to do a bulk replace
("tgext.authorization" -> "repoze.what") on our TurboGears applications when
we upgrade to the second beta. That would be the only change required in your
code.
In spite of the "new" project, this won't have negative effects in our
applications; no need to write more code, nor tweaks here and there. It will
keep playing nice with TurboGears, or even better.
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
-~----------~----~----~----~------~----~------~--~---
