Re: [Repoze-dev] No repoze.who.plugins.form in repoze 2.0a3

[Mathieu Leduc-Hamel]

Yesterday i had this error y trying repoze.bfg, and since i'm using
buildout, i've just add the magical flag: prefer-final = true.

But seriously maybe not having any beta or alpha version on Pypi would
be a better idea, i tend to think that for these development versions,
we should use another find-links, no ?

On Thu, Oct 28, 2010 at 11:34 AM, Tres Seaver tsea...@palladion.com wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 10/28/2010 08:54 AM, Roland Hedberg wrote:

 Probably fell out in the move from 1.X to 2.0 .
 Will it get back in or is it distributed as a separate package ?

 As noted in the changelog (visible on the PyPI page):

  http://pypi.python.org/pypi/repoze.who/

 the deprecated plugins are now available in a standalone package:

  http://pypi.python.org/pypi/repoze.who.deprecatedplugins

 Note that the plugins are deprecated becuase they force a twisted amount
 of coupling between the middleware (responsible for issueing the
 challenge, but also for scraping the form values from the subsequent
 POST) and the application (responsible for rendering the form).

 The preferred mode under repoze.who 2.0 is now to use the 'redirector'
 plugin to handle the challenge, and update the application view which
 renders the login form to also handle the POST, and use the repoze.who
 API object to validate and remember the credentials.  See:

  http://docs.repoze.org/who/2.0/configuration.html

 for the example configuration, and:

  http://docs.repoze.org/who/2.0/api.html#mixed-use-of-repoze-who-middleware-and-api

 for an example of implementing the login view.



 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/

 iEYEARECAAYFAkzJmBQACgkQ+gerLs4ltQ7SdQCghG7Zq/5OlNYUBU1bNxzPAv7T
 /gkAn0Aeo5DzI5/CxiCBx48E6RNyJFzI
 =6yGg
 -END PGP SIGNATURE-
 ___
 Repoze-dev mailing list
 Repoze-dev@lists.repoze.org
 http://lists.repoze.org/listinfo/repoze-dev




-- 
Mathieu Leduc-Hamel
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev

Re: [Repoze-dev] No repoze.who.plugins.form in repoze 2.0a3

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 10/28/2010 11:45 AM, Mathieu Leduc-Hamel wrote:
 Yesterday i had this error y trying repoze.bfg, and since i'm using
 buildout, i've just add the magical flag: prefer-final = true.
 
 But seriously maybe not having any beta or alpha version on Pypi would
 be a better idea, i tend to think that for these development versions,
 we should use another find-links, no ?

Nope.  If you are not ready to take whatever is latest-and-greatest for
your dependencies and live with the pain, then you need to manage that
explicitly, either by running your own index (which is what we do, for
the most part) or by pinning the dependencies (e.g., in buildout.cfg, or
your meta-package's install_requires).

Our rationale for running project-specific indexes is that running
production sites using PyPI-based deployment strategies is a
white-knockle ride:  better to created a walled garden subset of PyPI
where you control the changes.


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/

iEYEARECAAYFAkzJoB8ACgkQ+gerLs4ltQ75rgCcC2cbFXCJQaZ9tVuP3pELiTjW
4T0AmwSSJx7bi+8iuMVOlR5Q/uHTsDt6
=SMHq
-END PGP SIGNATURE-
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev