-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/02/2011 11:48 AM, Carsten Senger wrote: > --On Mittwoch, Februar 02, 2011 11:31:04 -0500 Tres Seaver > <tsea...@palladion.com> wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On 02/02/2011 09:33 AM, Wolfgang Schnerring wrote: >> >>> I see that there's a 1.x and 2.x line of repoze.who (2.x being in >>> alpha), but I can't seem to figure out what the main differenences are, >> >> The major effort for 2.0 was to factor out the plugin set into an API >> object which could be used from within your application, as well as >> supporting the "middleware" case. See: >> >> http://docs.repoze.org/who/2.0/narr.html#using-repoze-who-without-wsgi-mi >> ddleware >> >> http://docs.repoze.org/who/2.0/api.html#using-repoze-who-without-middlewa >> re >> >> http://docs.repoze.org/who/2.0/api.html#mixed-use-of-repoze-who-middlewar >> e-and-api > > It would be a good idea to make an alpha 4 release to catch up with the > docs on docs.repoze.org. API.login() and API.logout() are not part of alpha 3.
Good point. I have just pushed out a 2.0a4 release to PyPI. I'm working now to untangle the story about how docs get pushed to docs.repoze.org: look for the updated docs here soon: http://docs.repoze.org/who/2.0/ Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1JmcUACgkQ+gerLs4ltQ735QCeP65hLxVs+sHc3WL8M9jZgqav Nv8AoMt+hx1zML3MaN2tzbheYYFbvSce =rsg8 -----END PGP SIGNATURE----- _______________________________________________ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
