I got a response from Tres Seaver to some of the issues I raised in this MIR:
==== Thanks for the report! 1.0.18 is a long time ago now (almost 4 1/2 years). The latest release is 2.2, and there will likely be a 2.2.1 released in the near future. We are pretty unlikely to make another 1.x release, unless you (or somebody else) submits PRs for them (I just opened a '1.0-maintenance' branch, in case someone wants to tackle it): https://github.com/repoze/repoze.who/tree/1.0-maintenance Changes since 1.0.18 relevant to your issues: - - Made `htpasswd' plugin more isochronous (2.1). - - Deprecated plugins, moving them to a new 'repoze.who.deprecatedplugins' project (2.0a3): - 'repoze.who.plugins.cookie.InsecureCookiePlugin' - 'repoze.who.plugins.form.FormPlugin' - 'repoze.who.plugins.form.RedirectingFormPlugin' On the trunk, the SQL plugin issues you report should probably get some attention: I don't actually use it myself, which makes that trickier to think about. ==== It would be nice to use a more up-to-date version of repoze.who. Nearly five years out of date already, it would be nice to avoid being eleven years out of date at the end of the next LTS release. Thanks -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-pysaml2 in Ubuntu. https://bugs.launchpad.net/bugs/1407695 Title: [MIR] python-saml2, python-repoze.who, xmlsec1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pysaml2/+bug/1407695/+subscriptions -- Ubuntu-server-bugs mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
