Re: [Repoze-dev] repoze.who status
-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-middleware http://docs.repoze.org/who/2.0/api.html#using-repoze-who-without-middleware http://docs.repoze.org/who/2.0/api.html#mixed-use-of-repoze-who-middleware-and-api which version is recommended for general consumption, what the plans for finalizing 2.x are (and whether there's something the general public can do to help). The reason we aren't in beta yet is that we may still discover a missing feature while implementing apps against it. Testing 2.0 in a wider range of apps is the biggest help you can provide. Humm, I noticed that in Pyramid there is a RepozeWho1AuthenticationPolicy -- is that a recommendation to stick with 1.x for now? ;-) Nope. The 2.0 version is actually quite stable. Because the auth policy for 1.0 didn't require any install_requires dependency on repoze.who, it shipped with pyramid. The equivalent version for 2.0 *does* require repoze.who, and thus is factored into a separate pacakge: http://pypi.python.org/pypi/pyramid_who Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1JhsgACgkQ+gerLs4ltQ6BTgCeNjit7FE+J5YYTrQ0eTeNGm7e ajEAoKwIKmPJTFXK9oS/FMJkCzYGjkNw =Tmre -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] repoze.who status
--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. ..Carsten ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] repoze.who status
* Tres Seaver tsea...@palladion.com [2011-02-02 17:31]: which version is recommended for general consumption, what the plans for finalizing 2.x are (and whether there's something the general public can do to help). The reason we aren't in beta yet is that we may still discover a missing feature while implementing apps against it. Testing 2.0 in a wider range of apps is the biggest help you can provide. Humm, I noticed that in Pyramid there is a RepozeWho1AuthenticationPolicy -- is that a recommendation to stick with 1.x for now? ;-) Nope. The 2.0 version is actually quite stable. Because the auth policy for 1.0 didn't require any install_requires dependency on repoze.who, it shipped with pyramid. The equivalent version for 2.0 *does* require repoze.who, and thus is factored into a separate pacakge: http://pypi.python.org/pypi/pyramid_who Thanks for the pointer! I guess we'll give 2.0 a whirl, then. Wolfgang ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] repoze.who status
-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 Designhttp://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
