[Repoze-dev] Fwd: [Pyramid-checkins] Broken: Pylons/pyramid#1123 (master - ba0593a)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Unicode literals are a no-no for 3.2-compatibility: File /home/travis/virtualenv/python3.2.5/lib/python3.2/site-packages/translationstring-1.2-py3.2.egg/translationstring/__init__.py, line 239 msgid = u'%s\x04%s' % (context, tstring) ^ SyntaxError: invalid syntax - Forwarded Message Subject: [Pyramid-checkins] Broken: Pylons/pyramid#1123 (master - ba0593a) Date: Tue, 04 Nov 2014 23:21:56 + From: Travis CI notificati...@travis-ci.org To: pyramid-check...@lists.repoze.org Build Update for Pylons/pyramid - - Build: #1123 Status: Broken Duration: 3 minutes and 39 seconds Commit: ba0593a (master) Author: Michael Merickel Message: fix squashed docstring on set_request_property fixes #1436 View the changeset: https://github.com/Pylons/pyramid/compare/f8cee4b3021f...ba0593aa9488 View the full build log and details: https://travis-ci.org/Pylons/pyramid/builds/40006145 - -- You can configure recipients for build notifications in your .travis.yml file. See http://docs.travis-ci.com/user/notifications -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAlRaOtQACgkQ+gerLs4ltQ6vhACgirD6iDrhZt/t4faesFOysl+r CwEAn2bXX6fXi7Dxk0U4lnwAeobriRn8 =kPgJ -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org https://lists.repoze.org/mailman/listinfo/repoze-dev
Re: [Repoze-dev] [Pyramid-checkins] Broken: Pylons/pyramid#1123 (master - ba0593a)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/05/2014 10:44 AM, Wichert Akkerman wrote: On 05 Nov 2014, at 15:57, Tres Seaver tsea...@palladion.com wrote: Unicode literals are a no-no for 3.2-compatibility: How important is 3.2 compatibility? We don't ordinarily drop a supported Python version a non-major release. As a dependency for pyramid, if translationstring drops 3.2 compatiblity, we would need to pin it for release branches to versions which preserved it. Note that the classifiers for translationstring 1.2 still claim support back to 2.4: https://pypi.python.org/pypi/translationstring/1.2 although testing versions 2.6 with tox is no longer feasible. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAlRaVoYACgkQ+gerLs4ltQ4P8gCgh+OCSzYo9/Apd/Ifz5lIiVWK F0kAoMSHt4Vri2QjhpHNLCatJ+gFUnvf =NKAB -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org https://lists.repoze.org/mailman/listinfo/repoze-dev
[Repoze-dev] [Pylons/cartouche] 7bcab0: Build docs under tox.
Branch: refs/heads/master Home: https://github.com/Pylons/cartouche Commit: 7bcab083fa6cf722cf2ffa3f7968d5f45eb00614 https://github.com/Pylons/cartouche/commit/7bcab083fa6cf722cf2ffa3f7968d5f45eb00614 Author: Tres Seaver tsea...@palladion.com Date: 2014-04-16 (Wed, 16 Apr 2014) Changed paths: M tox.ini Log Message: --- Build docs under tox. Commit: f5530a3124ba88f287446a9f6f1ca9e4658a53cc https://github.com/Pylons/cartouche/commit/f5530a3124ba88f287446a9f6f1ca9e4658a53cc Author: Tres Seaver tsea...@palladion.com Date: 2014-04-16 (Wed, 16 Apr 2014) Changed paths: M cartouche/__init__.py M cartouche/tests/test_admin.py M cartouche/tests/test_login.py M cartouche/tests/test_registration.py M setup.py Log Message: --- Pull in pyramid_chameleon explicitly. Pyramid 1.5 no longer wires up Chameleon templates by default. Commit: 49cd7ca17360688bf262cad68e9ac6aae7a52a10 https://github.com/Pylons/cartouche/commit/49cd7ca17360688bf262cad68e9ac6aae7a52a10 Author: Tres Seaver tsea...@palladion.com Date: 2014-04-16 (Wed, 16 Apr 2014) Changed paths: M cartouche/models.py M cartouche/persistence.py M cartouche/pyramidpolicy.py M cartouche/testing.py M cartouche/whoplugin.py Log Message: --- Py3k: Replace class advice w/ class decorator. 'zope.interface.implements' - 'zope.interface.implementer'. Also, replace print statements. Commit: ef9f98adb8d304dbcc69831874ee4abb4881459b https://github.com/Pylons/cartouche/commit/ef9f98adb8d304dbcc69831874ee4abb4881459b Author: Tres Seaver tsea...@palladion.com Date: 2014-04-16 (Wed, 16 Apr 2014) Changed paths: M cartouche/login.py M cartouche/registration.py Log Message: --- Py3k: forward-compat exception syntax. Commit: 478aa293c6681790512103c3d8a53f50302f66b9 https://github.com/Pylons/cartouche/commit/478aa293c6681790512103c3d8a53f50302f66b9 Author: Tres Seaver tsea...@palladion.com Date: 2014-04-16 (Wed, 16 Apr 2014) Changed paths: A cartouche/_compat.py M cartouche/tests/test_registration.py M cartouche/util.py Log Message: --- Py3k: straddle imports. Commit: 0242ff4609f27bce562654638fc69ab355894876 https://github.com/Pylons/cartouche/commit/0242ff4609f27bce562654638fc69ab355894876 Author: Tres Seaver tsea...@palladion.com Date: 2014-04-16 (Wed, 16 Apr 2014) Changed paths: M cartouche/util.py Log Message: --- Py3k: dict.items no longer a list. Commit: 7da2c38b3613830ec2d7d676c2df7b682d766222 https://github.com/Pylons/cartouche/commit/7da2c38b3613830ec2d7d676c2df7b682d766222 Author: Tres Seaver tsea...@palladion.com Date: 2014-04-16 (Wed, 16 Apr 2014) Changed paths: M cartouche/tests/test_registration.py M cartouche/tests/test_util.py Log Message: --- Py3k: crypted passwords are bytes. Commit: 6972038abf5302aafafe8dd23baa64a3595e41fe https://github.com/Pylons/cartouche/commit/6972038abf5302aafafe8dd23baa64a3595e41fe Author: Tres Seaver tsea...@palladion.com Date: 2014-04-17 (Thu, 17 Apr 2014) Changed paths: M cartouche/_compat.py M cartouche/interfaces.py M cartouche/models.py M cartouche/pyramidpolicy.py M cartouche/registration.py M cartouche/tests/test_login.py M cartouche/tests/test_registration.py M cartouche/tests/test_util.py M cartouche/util.py M setup.py Log Message: --- Accomodate newer deform / pyramid. Avoid unicode literals (Python 3.2). Tests now pass on Python 3.2, 3.3. Commit: 55f95551f038647c7b4b31b7232977d8111d13b9 https://github.com/Pylons/cartouche/commit/55f95551f038647c7b4b31b7232977d8111d13b9 Author: Tres Seaver tsea...@palladion.com Date: 2014-04-17 (Thu, 17 Apr 2014) Changed paths: M cartouche/tests/test_login.py M cartouche/tests/test_persistence.py M cartouche/tests/test_registration.py M cartouche/tests/test_util.py M cartouche/tests/test_whoplugin.py Log Message: --- Py3k unit test nannyism. Commit: d2034b3bf51239921f0c81cd95abbc03e8bb4f4b https://github.com/Pylons/cartouche/commit/d2034b3bf51239921f0c81cd95abbc03e8bb4f4b Author: Tres Seaver tsea...@palladion.com Date: 2014-04-17 (Thu, 17 Apr 2014) Changed paths: M setup.py M tox.ini Log Message: --- Explicit support for Python 3.2 and 3.3. Commit: d20774bcb6695661ed0fe073ad0567b10518c66a https://github.com/Pylons/cartouche/commit/d20774bcb6695661ed0fe073ad0567b10518c66a Author: Tres Seaver tsea...@palladion.com Date: 2014-04-17 (Thu, 17 Apr 2014) Changed paths: M setup.py Log Message: --- Remove fossil. Commit: dafe36558a36cdc367908ffc60a1314975ccf974 https://github.com/Pylons/cartouche/commit/dafe36558a36cdc367908ffc60a1314975ccf974 Author: Tres Seaver
[Repoze-dev] [issue179] respoze.profile doesn't handle WSGI iterables properly.
Tres Seaver tsea...@agendaless.com added the comment: Released w/ 1.4. -- status: chatting - resolved __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue179 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org https://lists.repoze.org/mailman/listinfo/repoze-dev
[Repoze-dev] [issue157] Chameleon throws errors for translation strings that contain html elements with and without i18n:name attributes
Tres Seaver tsea...@agendaless.com added the comment: Please report / track Chameleon issues on Github: https://github.com/malthe/chameleon/issues -- status: chatting - deferred __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue157 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org https://lists.repoze.org/mailman/listinfo/repoze-dev
[Repoze-dev] [issue148] Chameleon does not pass on repeat variables to fill-slot snippets
Tres Seaver tsea...@agendaless.com added the comment: Please report / track Chameleon issues on Github: https://github.com/malthe/chameleon/issues -- status: unread - deferred __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue148 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org https://lists.repoze.org/mailman/listinfo/repoze-dev
[Repoze-dev] [issue139] Chameleon - can't create xml and doctype declarations from macro
Tres Seaver tsea...@agendaless.com added the comment: Please report / track Chameleon issues on Github: https://github.com/malthe/chameleon/issues -- status: chatting - deferred __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue139 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org https://lists.repoze.org/mailman/listinfo/repoze-dev
[Repoze-dev] [issue140] reversing the arg names of two-arg view callables causes a weird exception
Tres Seaver tsea...@agendaless.com added the comment: Please report / track Pyramid issues on Github: https://github.com/Pylons/pyramid/issues -- status: in-progress - deferred __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue140 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org https://lists.repoze.org/mailman/listinfo/repoze-dev
[Repoze-dev] [issue165] better normalized markup for deform widgets
New submission from Tres Seaver tsea...@agendaless.com: Please report / track deform issues on Github: https://github.com/Pylons/deform/issues -- status: unread - chatting __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue165 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org https://lists.repoze.org/mailman/listinfo/repoze-dev
[Repoze-dev] [issue113] repoze.bfg.jinja2 adding extension
Tres Seaver tsea...@agendaless.com added the comment: Please report / track pyramid_jinja2 issues on Github: https://github.com/Pylons/pyramid_jinja2/issues -- status: unread - deferred __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue113 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org https://lists.repoze.org/mailman/listinfo/repoze-dev
[Repoze-dev] [issue84] Brute force lockouts
Tres Seaver tsea...@agendaless.com added the comment: Please report / track repoze.who issues on Github: https://github.com/repoze/repoze.who/issues -- status: chatting - deferred __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue84 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org https://lists.repoze.org/mailman/listinfo/repoze-dev
[Repoze-dev] [issue153] config.scan() and test dependencies
Tres Seaver tsea...@agendaless.com added the comment: Please report / track venusian issues on Github: https://github.com/Pylons/venusian/issues __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue153 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org https://lists.repoze.org/mailman/listinfo/repoze-dev
[Repoze-dev] Putting bugs.repoze.org in read-only mode
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sorry for the spam from the tracker -- I've tried to close / defer all open issues on the old Repoze roundup issue tracker. I've removed all create / edit permos for non-admin users on http://bugs.repoze.org/, and directed folks to use Github instead for the actively-maintained projects. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlKw1qoACgkQ+gerLs4ltQ5cVwCgxgwYRoseQpR0/Y2GMxHBWj1I iY0AoIgibXIi7OQgMyUIBfUNpk9RJA1u =qf0o -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org https://lists.repoze.org/mailman/listinfo/repoze-dev
Re: [Repoze-dev] [issue49] Create the repoze.what LDAP plugin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/25/2013 09:29 AM, admin wrote: System message: __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue49 Sorry for the noise: fscking comment spammer. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlECm0oACgkQ+gerLs4ltQ5ZpQCfW9oqD3IfFq8XNf8XVxeeSSKP rTIAn3nRe8Kk2RlTqPgJOU+6U/Zy6zpn =U35r -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org https://lists.repoze.org/mailman/listinfo/repoze-dev
[Repoze-dev] Messed up List-Ids
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I noticed this morning that some list traffic was comming from the wrong domain, due to a Mailman admin error on my part yesterday. Apologies for the incovenience, Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlDR518ACgkQ+gerLs4ltQ6+/QCg01dFKdbBOCDHg62wxI6P0Mfn digAoMnnXCwlgpjxU3uLblXNl24P1Y4d =l3aS -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org https://lists.agendaless.com/mailman/listinfo/repoze-dev
Re: [Repoze-dev] [issue117] chapter 3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/09/2012 10:11 AM, Chris Withers wrote: spam much? ;-) That was a huge pile of attachment spam on the bug tracker: we need to clean that crap out, and figure out how to defeat it. Anybody know how to fix that in Roundup? Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlCdi4gACgkQ+gerLs4ltQ5u+gCgh1z1MurSQvGrqKZ41qbMICVN TrgAoKXKYXQRiTJvUxrNLaJnROy/BxPm =wqZK -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org https://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] Traditional email user authentication with Repoze.who
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/31/2012 07:54 AM, Dinesh B Vadhia wrote:
We want to implement a traditional Python-based email/password user
authentication system in a Tornado web application. The user login
details are to be held in a server database. Support for 'Forgot
email/password' would be a plus. Is this possible with Repoze.who?
I don't know much about Tornado, except that it is a non-WSGI server
based around non-blocking semantics. The repoze.who middleware is
therefore not a good fit, but you could still use the repoze.who API.
You would need to:
- - Configure the API factory at startup (e.g., with an INI file) [1]
- - On each request where you need an authenticated user, call the factory
to get an API object[1], and then call it's methods ('authenticate',
'remember', 'forget')[2].
See:
[1]
http://docs.repoze.org/who/2.0/api.html#using-repoze-who-without-middleware
[2] http://docs.repoze.org/who/2.0/api.html#repoze.who.interfaces.IAPI
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iEYEARECAAYFAlCRPicACgkQ+gerLs4ltQ5QFQCgrCvg18MKCI13QMP+jSPvY+pL
kY0An0wps+vNB/SiAoGmLzTsFIb4NUgs
=Agma
-END PGP SIGNATURE-
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue185] Repoze module doesn't contain __init__.py
Tres Seaver tsea...@agendaless.com added the comment: The packages do contain __init__.py: https://github.com/repoze/repoze.who/tree/master/repoze https://github.com/repoze/repoze.who/tree/master/repoze/who https://github.com/repoze/repoze.what/tree/master/repoze/what -- status: unread - resolved __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue185 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] Problems with basic usage of repoze.who 2.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/10/2012 06:41 PM, Chimezie Ogbuji wrote: Hello, I'm trying to follow instructions [1] on using repoze.who 2.0 as WSGI middleware from a configuration. After installing repoze.who 2.0 from a fresh copy from the git repository [2], I found I was unable to even import make_middleware_with_config without getting a Zope-related error. I was under the impression that repoze.who did not require Zope. The error I'm getting is from when I try from repoze.who.config import make_middleware_with_config The traceback is: Traceback (most recent call last): ..snip.. File repoze/who/config.py, line 8, in module from repoze.who.api import APIFactory File repoze/who/api.py, line 16, in module class APIFactory(object): File /System/Library/Frameworks/Python.framework/Versions/2.6/Extras/lib/python/zope/interface/declarations.py, line 495, in __call__ raise TypeError(Can't use implementer with classes. Use one of TypeError: Can't use implementer with classes. Use one of the class-declaration functions instead. I tried searching google and mailing lists for any mention of this, but couldn't find anything there or in the documentation for that matter. Can anyone tell me what I'm doing wrong? You need a newer version of zope.interface (3.6 or later). I recommend using a virtuaenv, so that whatever put the version you have doesn't break. E.g.:: $ /path/to/virtualenv --no-site-packages /path/to/your/project $ /path/to/your/project/bin/easy_install repoze.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.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/V6WsACgkQ+gerLs4ltQ4X2QCgnk/41oIrol4rQgg4yVt0eJBW NyUAn1pK9PKRvrqGqnZcnJq/IYMBKubK =8FHj -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] User gets logged out to early
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/01/2012 02:07 AM, Cornelius Kölbel wrote: I am using repoze.who 1.0.18 with pylons to authenticate some users within my application. But the strange thing is, that the timeout does not seem to work properly. The timeout was set to 3000 and the reissue_time to 1000, but the user is logged out much much earlier. And And even if he navigates through the UI, he gets logged out after about 5 or 10 minutes. My who.ini looks like below. Thanks for any hint. Kind regards Cornelius [plugin:form] use = repoze.who.plugins.form:make_redirecting_plugin #use = lseappliance.lib.repoze_who_pam::make_redirecting_plugin login_form_url = /account/login login_handler_path = /account/dologin logout_handler_path = /account/logout rememberer_name = auth_tkt [plugin:auth_tkt] use = repoze.who.plugins.auth_tkt:make_plugin secret = WCD9jL3CD8secDUf timeout = 3600 reissue_time = 1800 #secure = true #include_ip = true cookie_name = lseappliance_who [general] request_classifier = repoze.who.classifiers:default_request_classifier challenge_decider = repoze.who.classifiers:default_challenge_decider [identifiers] plugins = form;browser auth_tkt [authenticators] plugins = lseappliance.lib.repoze_who_pam:PamAuthenticatorPlugin [challengers] plugins = form;browser Those settings all look normal to me (1800 and 3600 instead of the 1000 and 3000 you reported, but still OK). Can you try turning on live headers and watch the cookies being set as you browse? BTW, your original message got stuck in the moderator queue because you aren't subscribed: if you want to avoid such delays, please subscribe (this list is really pretty low volume and high signal-to-noise ratio). 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/ iEYEARECAAYFAk+f51kACgkQ+gerLs4ltQ5FZACeIbsAtKf2aC9oLxSO5y4jwM07 9jUAoKo6EjJmSpfqwqw9/OOrawRpjwTr =WpdF -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] Help customizing Repoze in turbogears
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/13/2012 10:58 AM, Jim Carroll wrote:
Hi, I'm struggling a bit to get rid of the friendly form identifier
and challenger, and do my own Authenticator in a turbogears 2.1
project.
I've got a 'faceless' web services server that won't even have a
login form, since no human will ever visit the site. So I want to
retain the session cookie mechanism, and the sa_auth module that uses
the default Group, User, and Permission model in SQL Alchemy. I just
am going to do my own Authentication, and get rid of the Challenger.
Are you authenticating clients based on the subnet, or something?
Otherwise you need a chellenger of some sort. Note that you may still
need some kind of challenger to cope with requests which come from
hostile / random sources.
So far I've implemented an IAuthenticator
class ShaAuthenticator(IAuthenticator): #implements(IAuthenticator)
def authenticate(self, environment, identity):
if not 'user_email' in identity: return None ...
and in app_cfg.py
hash_auth = ShaAuthenticator base_config.sa_auth.authenticators =
[('hash_auth', hash_auth)]
# got rid of the challenger base_config.sa_auth.form_plugin = None
#and am keeping base_config.auth_backend = 'sqlalchemy'
base_config.sa_auth.dbsession = model.DBSession
If I try to run at the moment I see:
ValueError: hash_auth: An object has failed to implement interface
InterfaceClass repoze.who.interfaces.IAuthenticator
The authenticate attribute was not provided.
I didn't find much help on the turbogears google group, I'm hoping
someone might be able to point me in the right direction here.
Thanks,
I'm not quite sure what else might be going on, but I do see that you
haven't created an instance of ShaAuthenticator. You have also commented
out the 'implements' class advisor.
FWIW, I ususally have unit tests like the following for classes that are
supposed to implement a given interface::
class MyObjTests(unittest.TestCase):
def _getTargetClass(self):
from mypackage.myobj import MyObj
return MyObj
def _makeOne(self, *args, **kw):
return self._getTargetClass()(*args, **kw)
def test_class_conforms_to_IFoo(self):
from zope.interface.verify import verifyClass
from whatever.package.interfaces import IFoo
verifyClass(IFoo, self._getTargetClass()
def test_instance_conforms_to_IFoo(self):
from zope.interface.verify import verifyObject
from whatever.package.interfaces import IFoo
verifyObject(IFoo, self._makeOne())
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/
iEYEARECAAYFAk+K9x4ACgkQ+gerLs4ltQ6iMACg1++sKpy5PoKcrmL+O6GrgMRq
meAAoNBQCo8ZqS9TTOhsHfxIlz/3N9Gu
=Flae
-END PGP SIGNATURE-
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [Pylons/cartouche] 118b49: Ignore derived.
Branch: refs/heads/master Home: https://github.com/Pylons/cartouche Commit: 118b4943c32b14962127d3b0ab78ef8ce5ac31b1 https://github.com/Pylons/cartouche/commit/118b4943c32b14962127d3b0ab78ef8ce5ac31b1 Author: Tres Seaver tsea...@palladion.com Date: 2012-04-04 (Wed, 04 Apr 2012) Changed paths: M .gitignore Log Message: --- Ignore derived. ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] repoz.what-x509
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/15/2012 05:35 PM, Arturo Sevilla wrote: I just finished building a plugin for repoze.what that enables authorization for X509 client certificates. It basically consists of two predicates (is_issuer and is_subject) which can check for any X509 attribute field. It also has an IIdentifier which returns credentials according to a specified x509 field. It still is in alpha, because I'm open to suggestions or any feature you may want. It has full unit test coverage and I'm making the documentation (I haven't finished it). You can see the repository at: https://github.com/arturosevilla/repoze.what-x509 The documentation at: http://readthedocs.org/docs/repozewhat-x509/en/latest/ This looks really interesting. I'd like to be able to use the identifier without the 'repoze.what' dependency: would you consider supporting a 'repoze-who-x509' version which split out the code in the current '__init__.py' (the identifier) and 'utils.py'? The r.what package would then depend on it, and import symbols from it. I would be glad to do the work of splitting it, if you would take such a patch (really, a new repo / tarball for the 'r.who' bits plus the patch to make the 'r.what' version use it). 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/ iEYEARECAAYFAk9pExkACgkQ+gerLs4ltQ7xPwCgrRq9H6e71kTkAQJdlCGt1lUb grkAoNOSruPI5vPD3s5TxBJ86p65ILz6 =0gE7 -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue146] repoze.who should support manual setting of cookie domain
Tres Seaver tsea...@agendaless.com added the comment: Pending a patch. -- status: chatting - deferred __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue146 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue182] make repoze.who to support py3k
Tres Seaver tsea...@agendaless.com added the comment: See: https://github.com/repoze/repoze.who/pull/3 -- status: chatting - in-progress __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue182 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue70] ZMI undo tab always reports There are no transactions that can be undone
New submission from Tres Seaver tsea...@agendaless.com: Given that Zope 2.12.23 and 2.13.13 are released, we're unlikely to make another release of reopze.zope2 for anything other than a major security bug. -- status: unread - deferred __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue70 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue37] 2.10 zopelib ships without top-level ImageFile module
Tres Seaver tsea...@agendaless.com added the comment: Given that Zope 2.12.23 and 2.13.13 are released, we're unlikely to make another release of zopelib for anything other than a major security bug. -- status: chatting - deferred __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue37 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue43] Logging for repoze.tm2
Tres Seaver tsea...@agendaless.com added the comment: The patch looks reasonable, although I might drop the logging on 'commit' (the by-far most frequent case, and effectively unintersting). -- nosy: +chrism, tseaver __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue43 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue158] Printer friendly CSS for the docs.repoze.org
Tres Seaver tsea...@agendaless.com added the comment: Thanks for the patch. I have applied it to the site. -- status: unread - resolved __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue158 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue183] [Patch] Have repoze.sphinx.autointerface interfaces included in Sphinx automudule listings.
Tres Seaver tsea...@agendaless.com added the comment: Thanks for the patch. I have merged it for the next release. -- status: unread - resolved __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue183 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue181] repoze.zope2 does not notify ZPublisher.pubevents
Tres Seaver tsea...@agendaless.com added the comment: We won't make another feature release for repoze.zope2. -- status: chatting - done-cbb __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue181 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] login by apy of repoze 1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/11/2012 05:36 PM, alex bodnaru wrote:
hello friends,
thanks again for repoze.*
Glad you find them useful!
one question: i've seen an api login method for repoze 2.
from repoze.who.api import get_api who_api = get_api(request.environ)
authenticated, headers = \ who_api.login(dict(login=Login,
password=UserPass))
how could i login a user in a program using repoze 1?
You have put your finger on it: The separate API is really the major new
feature in r.who 2.0.
i came up with the following solution, but is it the best way to go?
plugins = request.environ.get('repoze.who.plugins').values()
rememberers = [auth for auth in plugins if hasattr(auth, 'remember')]
res = rememberers and \ rememberers[0].remember(request.environ,
dict(login=Login, password=UserPass))
That is pretty much the required workaround for the lack of an API in
r.who 1.x.
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/
iEYEARECAAYFAk9dHXAACgkQ+gerLs4ltQ6qNACfcIuAfVIQQpc5+d/1LnFg6F/I
DrUAoLX4+JQ2hSx40ZoeWEGh1xBv4kW4
=AUsh
-END PGP SIGNATURE-
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue64] repoze.zope2 not compatible with zope 2.12 browser resources
Tres Seaver tsea...@agendaless.com added the comment: It is pretty unlikely that we will relese another version of repoze.zope2. __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue64 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [Pylons/cartouche] 84f6f0: Ensure '_static' is present under git.
Branch: refs/heads/master Home: https://github.com/Pylons/cartouche Commit: 84f6f01b01b0f0462e336b2d8a6b08467e3e57e0 https://github.com/Pylons/cartouche/commit/84f6f01b01b0f0462e336b2d8a6b08467e3e57e0 Author: Tres Seaver tsea...@palladion.com Date: 2011-11-09 (Wed, 09 Nov 2011) Changed paths: A docs/_static/README.txt Log Message: --- Ensure '_static' is present under git. git doesn't track empty directories, whereas bzr did. Commit: d3b3bcc29607a12fe810fa976d9efbb07ad7d654 https://github.com/Pylons/cartouche/commit/d3b3bcc29607a12fe810fa976d9efbb07ad7d654 Author: Tres Seaver tsea...@palladion.com Date: 2011-11-09 (Wed, 09 Nov 2011) Changed paths: M .gitignore Log Message: --- Ignore derived docs. Compare: https://github.com/Pylons/cartouche/compare/8ed9486...d3b3bcc ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [Pylons/cartouche] dbaf62: Ensure that the 'var' directory is present on firs...
Branch: refs/heads/master Home: https://github.com/Pylons/cartouche Commit: dbaf62ed79fb71c5eb3656b7a8e59756af311a7b https://github.com/Pylons/cartouche/commit/dbaf62ed79fb71c5eb3656b7a8e59756af311a7b Author: Tres Seaver tsea...@palladion.com Date: 2011-11-08 (Tue, 08 Nov 2011) Changed paths: A var/README.txt Log Message: --- Ensure that the 'var' directory is present on first checkout. ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [Pylons/cartouche] 5e7d3c: Move the admin view into the main configuretion.
Branch: refs/heads/master Home: https://github.com/Pylons/cartouche Commit: 5e7d3c9a9025bb351bd8322f1a558fd280fc41fc https://github.com/Pylons/cartouche/commit/5e7d3c9a9025bb351bd8322f1a558fd280fc41fc Author: Tres Seaver tsea...@palladion.com Date: 2011-11-08 (Tue, 08 Nov 2011) Changed paths: M cartouche/configure.zcml M cartouche/homepage.zcml Log Message: --- Move the admin view into the main configuretion. Commit: e02ed3feb792e00b04f573166cd7790babe002e4 https://github.com/Pylons/cartouche/commit/e02ed3feb792e00b04f573166cd7790babe002e4 Author: Tres Seaver tsea...@palladion.com Date: 2011-11-08 (Tue, 08 Nov 2011) Changed paths: M cartouche/configure.zcml Log Message: --- Normalize registration of views against interfaces. Commit: 8ed9486e53e62d417e49ae8bbabe122ec75270f3 https://github.com/Pylons/cartouche/commit/8ed9486e53e62d417e49ae8bbabe122ec75270f3 Author: Tres Seaver tsea...@palladion.com Date: 2011-11-08 (Tue, 08 Nov 2011) Changed paths: M cartouche/admin.py M cartouche/configure.zcml M cartouche/templates/admin.pt A cartouche/templates/admin_registration.pt Log Message: --- Flesh out the admin UI a bit. Compare: https://github.com/Pylons/cartouche/compare/dbaf62e...8ed9486 ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [Pylons/cartouche] de938c: Fix test breakage.
Branch: refs/heads/master Home: https://github.com/Pylons/cartouche Commit: de938c29c35b32e950a67a7dc375cbc872c031e6 https://github.com/Pylons/cartouche/commit/de938c29c35b32e950a67a7dc375cbc872c031e6 Author: Tres Seaver tsea...@palladion.com Date: 2011-11-07 (Mon, 07 Nov 2011) Changed paths: M cartouche/tests/test_login.py M cartouche/tests/test_registration.py Log Message: --- Fix test breakage. Commit: 287797a03d78eb90da905d7b4642fdea1ec2a5cb https://github.com/Pylons/cartouche/commit/287797a03d78eb90da905d7b4642fdea1ec2a5cb Author: Tres Seaver tsea...@palladion.com Date: 2011-11-07 (Mon, 07 Nov 2011) Changed paths: M cartouche/tests/test_pyramidpolicy.py Log Message: --- Merge / resolve. Compare: https://github.com/Pylons/cartouche/compare/28477b5...287797a ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [Pylons/cartouche] a6463b: Ignore var
Branch: refs/heads/master Home: https://github.com/Pylons/cartouche Commit: a6463b1296af098778054cdaa80006b110775d1e https://github.com/Pylons/cartouche/commit/a6463b1296af098778054cdaa80006b110775d1e Author: Tres Seaver tsea...@palladion.com Date: 2011-11-07 (Mon, 07 Nov 2011) Changed paths: M .gitignore Log Message: --- Ignore var ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [Pylons/cartouche] ee8fb9: Make the 'no_mail' app use the ZODB.
Branch: refs/heads/master Home: https://github.com/Pylons/cartouche Commit: ee8fb90378fb2849fe4ec75ee944c906a128a627 https://github.com/Pylons/cartouche/commit/ee8fb90378fb2849fe4ec75ee944c906a128a627 Author: Tres Seaver tsea...@palladion.com Date: 2011-11-07 (Mon, 07 Nov 2011) Changed paths: M cartouche/no_mail.zcml Log Message: --- Make the 'no_mail' app use the ZODB. Commit: 468f6054afbcdd9f63782751abb8764b7d648f82 https://github.com/Pylons/cartouche/commit/468f6054afbcdd9f63782751abb8764b7d648f82 Author: Tres Seaver tsea...@palladion.com Date: 2011-11-07 (Mon, 07 Nov 2011) Changed paths: M development.ini Log Message: --- Redirect to the homepage after editing the profile. Compare: https://github.com/Pylons/cartouche/compare/a6463b1...468f605 ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [Pylons/cartouche] 40ccb4: Better wiring for 'no_mail' profile.
Branch: refs/heads/master Home: https://github.com/Pylons/cartouche Commit: 40ccb406405b9de0107e322ec42e66c4ec6e2c31 https://github.com/Pylons/cartouche/commit/40ccb406405b9de0107e322ec42e66c4ec6e2c31 Author: Tres Seaver tsea...@palladion.com Date: 2011-11-07 (Mon, 07 Nov 2011) Changed paths: M cartouche/no_mail.zcml Log Message: --- Better wiring for 'no_mail' profile. Include the 'home_page' profile and then supply the no-mail adapter. ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [Pylons/cartouche] dd7dcc: Add storage for group info.
Branch: refs/heads/master Home: https://github.com/Pylons/cartouche Commit: dd7dcc06bd45119d50c0dc414e7aeb0d2a202785 https://github.com/Pylons/cartouche/commit/dd7dcc06bd45119d50c0dc414e7aeb0d2a202785 Author: Tres Seaver tsea...@palladion.com Date: 2011-11-07 (Mon, 07 Nov 2011) Changed paths: M TODO.txt M cartouche/interfaces.py M cartouche/models.py Log Message: --- Add storage for group info. Commit: acb1fa70bc5d1ef4f34d27864fa2a59ce0fa9f37 https://github.com/Pylons/cartouche/commit/acb1fa70bc5d1ef4f34d27864fa2a59ce0fa9f37 Author: Tres Seaver tsea...@palladion.com Date: 2011-11-07 (Mon, 07 Nov 2011) Changed paths: M TODO.txt A cartouche/admin.py M setup.py Log Message: --- Add a command-line script to make an existing user an admin. Commit: 074dfe020231efd00db41017fae4f6c200333ca0 https://github.com/Pylons/cartouche/commit/074dfe020231efd00db41017fae4f6c200333ca0 Author: Tres Seaver tsea...@palladion.com Date: 2011-11-07 (Mon, 07 Nov 2011) Changed paths: M TODO.txt M cartouche/pyramidpolicy.py Log Message: --- Extend effective_principals to include groups defined in admin UI. Commit: 2d182645f69cb4548ae996384650b2cda99c5b1e https://github.com/Pylons/cartouche/commit/2d182645f69cb4548ae996384650b2cda99c5b1e Author: Tres Seaver tsea...@palladion.com Date: 2011-11-07 (Mon, 07 Nov 2011) Changed paths: M TODO.txt M cartouche/admin.py M cartouche/homepage.zcml M cartouche/models.py A cartouche/templates/admin.pt Log Message: --- Add an admin overview view showing pending / confirmed users. Compare: https://github.com/Pylons/cartouche/compare/40ccb40...2d18264 ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [Pylons/cartouche] fb1198: Test repair.
Branch: refs/heads/master Home: https://github.com/Pylons/cartouche Commit: fb11982955129766061141706789af911049ed05 https://github.com/Pylons/cartouche/commit/fb11982955129766061141706789af911049ed05 Author: Tres Seaver tsea...@palladion.com Date: 2011-11-07 (Mon, 07 Nov 2011) Changed paths: M cartouche/tests/test_pyramidpolicy.py Log Message: --- Test repair. ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [Pylons/cartouche] 24ac72: Scrub some nastiness from admin view markup.
Branch: refs/heads/master Home: https://github.com/Pylons/cartouche Commit: 24ac72eeb59c6b6e253495262f4200252f3834e7 https://github.com/Pylons/cartouche/commit/24ac72eeb59c6b6e253495262f4200252f3834e7 Author: Tres Seaver tsea...@palladion.com Date: 2011-11-07 (Mon, 07 Nov 2011) Changed paths: M cartouche/templates/admin.pt Log Message: --- Scrub some nastiness from admin view markup. ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] mod_uwsgi always sets REMOTE_USER
On 10/18/2011 02:58 PM, Petr Blahos wrote: Hi all, I came across a strange problem, when my Python app using repoze.who works on Apache and mod_wsgi but stops working when running on Apache mod_uwsgi -- uwsgi. (by not working I mean that repoze.who seemed to be completely by-passed). Which I later realized was caused by a condition in repoze.who middleware: if self.remote_user_key in environ: # act as a pass through if REMOTE_USER (or whatever) is # already set return self.app(environ, start_response) and the fact that mod_uwsgi always sets REMOTE_USER. When asking on uWSGI list I got this response: http://lists.unbit.it/pipermail/uwsgi/2011-October/002780.html so I am asking here if there are any thoughts on this? Stuffing REMOTE_USER into the request willy-nilly may be allowed by the spec, but it is stupid. Section 4.1 of that RFC says: An optional meta-variable may be omitted (left unset) if its value is NULL. Nevertheless, I would be willing to merge a pull request which bypassed the bypass if the value was empty. Such a patch should also include a test showing the new behavior. Tres. -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue174] repoze.who 2.0a3 doesn't respect the WSGI PEP
Tres Seaver tsea...@agendaless.com added the comment: I have committed an extension of the fix for the 2.0 final release which closes the iterable before raising the RuntimeError when no challenger is available. -- status: chatting - resolved __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue174 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue66] remove port from cookie path
Tres Seaver tsea...@agendaless.com added the comment: Fix committed for the 2.0 final release. -- status: chatting - resolved __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue66 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue99] max_age in repoze.who-friendlyform
Tres Seaver tsea...@agendaless.com added the comment: The form plugins are deprecated, and no longer distributed with repoze.who 2.0: http://svn.repoze.org/repoze.who.deprecatedplugins/tags/2.0/ -- status: unread - deferred __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue99 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue89] AuthTktPlugin fails with Opera, if non-standard port used
Tres Seaver tsea...@agendaless.com added the comment: This is indeed a duplicate of issue55. The port is now stripped on the trunk: this fix should appear in the 2.0 final release. -- status: chatting - resolved __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue89 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] Announce: repoze.who 2.0 final released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On behalf of the repoze developers, I am pleased to announce the 2.0 release of the repoze.who authentication / authorization framework for Python web applications. Major features == - - Refactored the core framework to permit usage as an API from within application code (e.g., for tighter integration of views such as login forms). Applications using 'repoze.who'` now fall into one of three catgeories: - - middleware-only applications are configured with middleware, and use either 'REMOTE_USER' or 'repoze.who.identity' from the environment to determing the authenticated user. - - bare metal applications use no 'repoze.who' middleware at all: instead, they configure and an 'APIFactory' object at startup, and use it to create an 'API' object when needed on a per-request basis. - - hybrid applications are configured with 'repoze.who' middleware, but use a new library function to fetch the 'API' object from the environ, e.g. to permit calling 'remember' after a signup or successful login. - - Enabled standard use of logging module's configuration mechanism. Deprecations - - Deprecated the following plugins, moving their modules, tests, and docs to a new project, 'repoze.who.deprecatedplugins': - - 'repoze.who.plugins.cookie.InsecureCookiePlugin' (applications should use 'repoze.who.plugins.auth_tkt.AuthTktPlugin' instead). - - 'repoze.who.plugins.form.FormPlugin' (applications should implement their own login forms, and use the new 'repoze.who.plugins.redirector.Redirector' plugin to issue the appropriate challenge). - - 'repoze.who.plugins.form.RedirectingFormPlugin' (applications should implement their own login forms, and use the new 'repoze.who.plugins.redirector.Redirector' plugin to issue the appropriate challenge). Backward Incompatibilities ~~ - - The middleware used to allow identifier plugins to pre-authenticate an identity. This feature is no longer supported: the 'auth_tkt' plugin, which used to use the feature, is now configured to work as an authenticator plugin (as well as an identifier). - - The 'repoze.who.middleware:PluggableAuthenticationMiddleware' class no longer has the following (non-API) methods (now made API methods of the 'repoze.who.api:API' class): - - 'add_metadata' - - 'authenticate' - - 'challenge' - - 'identify' - - The following (non-API) functions moved from 'repoze.who.middleware' to 'repoze.who.api': - - 'make_registries' - - 'match_classification' - - 'verify' Please report bugs to the repoze bug tracker: http://bugs.repoze.org/ Questions should be directed to the 'repoze-dev@lists.repoze.org' mailing list. Enjoy! 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/ iEYEARECAAYFAk6DdqYACgkQ+gerLs4ltQ7jqACfd38u5XScdDC7Qq3lyUeY0lZF 81MAn3FMSr20vYt+ToioRiei2ekBvfh8 =3nSc -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] Different auth method on different pages, possible ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/23/2011 06:48 AM, Roland Hedberg wrote: I wonder how, if possible, one would configure repoze.who to use different auth method for different pages ? More specifically I'd like to use basic auth for one page and form login for another. The 'request_classifier' component is responsible for sniffing the environ and returning a string label for the request type[1]. You can define a custom classifier, and then associate plugins only with requests having the appropriate label[2]. [1] See how the 'default_request_classifier' does this: https://github.com/repoze/repoze.who/blob/master/repoze/who/classifiers.py [2] The example configuration does this for the 'redirector' plugin (the one which sends the user to the login form): http://docs.repoze.org/who/2.0/configuration.html#configuring-repoze-who-via-config-file 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/ iEYEARECAAYFAk585Z0ACgkQ+gerLs4ltQ7TuACdHlxQQIGxVKBa2JHXHrr9AcwI 8IEAoMsS1FAnGni2myzJrwLqqcII+C7m =0Ude -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] weird intermittent error with apache2 and mod_wsgi
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/27/2011 11:36 AM, Chris Withers wrote: RuntimeError: class.__dict__ not accessible in restricted mode Let me google that for you: - - http://mail.zope.org/pipermail/zodb-dev/2009-June/012607.html - - http://mediacore.com/blog/hosting-multiple-wsgi-applications-with-apache/ - - http://trac.edgewall.org/ticket/3371 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/ iEYEARECAAYFAk4IsFoACgkQ+gerLs4ltQ5VIwCgsoZ7ujvlOsZ+U+YAiPushoyF Dm4AniLcNiyWrbPuIHOpS8zNmAW0B2lZ =4gYU -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] repoze.what.plugins.sql 1.0 and SQLAlchemy 0.7
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/06/2011 11:03 PM, Nathan wrote: Hopefully this is the right place to post this. The repoze bug tracker appears to be down so I couldn't post it there, either. I have restarted the roundup instance. Current development of repoze.what has moved from the Repoze SVN repository to Github: https://github.com/repoze/repoze.what/ New bug reports for repoze.what should likely got to the Github tracker. I've been testing out SQLAlchemy 0.7b3 in my app and, while it's gone quite well for the most part, it breaks due to this import in repoze.what.plugins.sql.adapters-1.0: from sqlalchemy.exceptions import SQLAlchemyError Apparently .exceptions has been removed in 0.7 (it's now .exc), but in any case, this import is not used anywhere in this module, and removing it has no ill effect as far as I can tell. Is there any chance a new version of this plugin could be released with this import removed? Our preferred mode for this kind of request is for the reporter to fork the repository, push the requested changes to the fork, and issue a pull request (bog-standard Github interaciton). We need to update the hacking repoze docs[1] to indicate the new model for the project moved to Github. [1] http://docs.repoze.org/hacking/ 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/ iEYEARECAAYFAk2d4f4ACgkQ+gerLs4ltQ4YBwCfUY1fGhsd1HSggEsnTgSV9gYR Up4AoKob71Ahl0Ql4uTQBWOtVhoGZ1Mj =zsd/ -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] Migration to Github
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/24/2011 07:02 AM, Brian Sutherland wrote:
On Tue, Feb 22, 2011 at 09:40:38AM -0500, Tres Seaver wrote:
After working with git / Github on the Pylons project, we have decided
to move the active / supported repoze.* projects over to Github,
under a new organization:
https://github.com/repoze
I'd like to make a new release of repoze.bitblt (when my pull request is
accepted). Is there any documentation anywhere about how releases should
be tagged/created within the Repoze github repository?
I have merged the pull request, and added you ('jinty') to a new team
which has push rights to the repoze.bitblt repository.
We haven't documented the release model because nobody but us chickens
has been making releases. Essentially, we are just making simple tags
in git for a release before pushing the tarball to the cheeseshop.
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/
iEYEARECAAYFAk2LQeQACgkQ+gerLs4ltQ64TACg1HuLO+iUXhwUN+/lwh9zDCCu
3TsAoMcBVal18HnW/EIiDkCmxbnuoUG6
=FUFF
-END PGP SIGNATURE-
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue162] [repoze.debug] Don't depend on 'threadframe'
Tres Seaver tsea...@agendaless.com added the comment: Thanks very much for the patch. Merged via the github pull request: https://github.com/repoze/repoze.debug/pull/1 -- status: unread - resolved __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue162 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue163] [repoze.debug] Don't crash if unicode presents while dumping thread states
Tres Seaver tsea...@agendaless.com added the comment: Thanks very much for the patch. Merged via the github pull request: https://github.com/repoze/repoze.debug/pull/1 -- status: unread - resolved __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue163 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue171] repoze.retry fails if environ[CONTENT_LENGTH] == ''
Tres Seaver tsea...@agendaless.com added the comment: https://github.com/repoze/repoze.retry/commit/7e98123e6bc170deda2f5f95857b2827ff3dd28f -- status: chatting - resolved __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue171 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] Migration to Github
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/22/2011 10:54 AM, Brian Sutherland wrote: On Tue, Feb 22, 2011 at 09:40:38AM -0500, Tres Seaver wrote: We have chosen to leave dormant projects in SVN for the indefinite future.. Please let us know if there is an existing 'repoze.*' project which you think needs to be migrated: repoze.bitblt is also used and maintained. Now moved to github: https://github.com/repoze/repoze.bitblt 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/ iEYEARECAAYFAk2Inb8ACgkQ+gerLs4ltQ51VQCeKwRxozI7a243tgQ4vKYUhrly iRgAn1YCmVxdL/IVDf6KvTekm1Dn/bGk =Vda2 -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] Migration to Github
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/22/2011 09:40 AM, Tres Seaver wrote: These packages are all now moved to github: - [X] repoze.accelerator - [X] repoze.browserid - [X] repoze.catalog - [X] repoze.component - [X] repoze.configuration - [X] repoze.debug - [X] repoze.errorlog - [X] repoze.folder - [X] repoze.lemonade - [X] repoze.lru - [X] repoze.mailin - [X] repoze.profile - [X] repoze.retry - [X] repoze.sendmail - [X] repoze.sphinx.autointerface - [X] repoze.tm2 - [X] repoze.who - [X] repoze.workflow - [X] repoze.zcml - [X] repoze.zodbconn 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/ iEYEARECAAYFAk2IniIACgkQ+gerLs4ltQ7ULgCfSj1YC1KAevbE649DAqBBCK+2 MesAn3Khl2w9ZSyzm3zar1yvEUrQ27CZ =07SD -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] Migration to Github
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/22/2011 09:02 AM, Wichert Akkerman wrote: On 3/22/11 14:01 , Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/22/2011 09:54 AM, Wichert Akkerman wrote: On 2/22/11 15:40 , Tres Seaver wrote: We have chosen to leave dormant projects in SVN for the indefinite future.. Please let us know if there is an existing 'repoze.*' project which you think needs to be migrated: repoze.filesafe is still actively maintained and used, so it should probably be added to the list. Now moved to github: https://github.com/repoze/repoze.filesafe Is there still a way for me to commit to it now? The general procedure is now like so: - - Fork the repository you are interested in. - - Sign CONTRIBUTORS.txt by adding your name and the date to the bottom. - - Commit and push your fork. - - Issue a pull request back to the original repository. Chris or I will then merge that pull request and add you to the appropriate team, which gives you the right to push to the main repository. 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/ iEYEARECAAYFAk2InwAACgkQ+gerLs4ltQ7gywCfRGPoqrMEhVPI1wcMPkesFVp9 JAUAnRXqBZxhnpQGmBGwE1B7eUMCOF1Q =nhn9 -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] Migration to Github
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/22/2011 10:13 AM, Laurence Rowe wrote: On 22 February 2011 14:40, Tres Seaver tsea...@palladion.com wrote: We have chosen to leave dormant projects in SVN for the indefinite future.. Please let us know if there is an existing 'repoze.*' project which you think needs to be migrated: Please migrate repoze.xmliter. I'm maintaining this for use with plone.app.theming / diazo (xdv). Done. Please fork, sign COMMITTERS.txt, commit / push, and do a pull request: https://github.com/repoze/repoze.xmliter 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/ iEYEARECAAYFAk2IttYACgkQ+gerLs4ltQ7bMQCfSy/jqbyIfbTXpOYWI/bvBfE7 p3UAoNtrCreX1mzYiJQ2vZTUzAgELVJA =Zvpy -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue177] repoze.sendmail is creating message ID in incorrectly
Tres Seaver tsea...@agendaless.com added the comment: This analysis sounds correct to me. -- assignedto: chrism - tseaver nosy: +tseaver status: unread - chatting __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue177 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] Migration to Github
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 After working with git / Github on the Pylons project, we have decided to move the active / supported repoze.* projects over to Github, under a new organization: https://github.com/repoze At this point, the following packages have been migrated to the Pylons project: - - [X] colander - - [X] deform - - [X] peppercorn - - [X] translationstring - - [X] venusian And we are in the process of moving these projects (those marked with a slash are in progress): - - [X] repoze.accelerator - - [X] repoze.browserid - - [X] repoze.catalog - - [X] repoze.component - - [X] repoze.configuration - - [X] repoze.debug - - [/] repoze.errorlog - - [/] repoze.folder - - [/] repoze.lemonade - - [/] repoze.lru - - [/] repoze.mailin - - [/] repoze.profile - - [/] repoze.retry - - [/] repoze.sendmail - - [/] repoze.sphinx.autointerface - - [/] repoze.tm2 - - [/] repoze.who - - [X] repoze.workflow - - [X] repoze.zcml - - [X] repoze.zodbconn We have chosen to leave dormant projects in SVN for the indefinite future.. Please let us know if there is an existing 'repoze.*' project which you think needs to be migrated: As each project moves, we are deleting the trunk and any branches in SVN, leaving behind a README pointing to the new Github repository. The new repositoris will contain migrated tags and significant branches, as well as the trunk. For contributor agreements, we are adopting the pattern we uses for the Pylons / Pyramid code on Github: contributors sign the agreement via the commit in which they add themselves to the list of signers of the agreement, maintained in the repository as 'CONTRIBUTORS.txt'. In order to bootstrap the new reopsitories, contributors who wish to continue contributing to one of the migrated repositories need to fork the repository of interest, and then add themselves to the signers in CONTRIBUTORS.txt. They should then submit a pull request for their fork. 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/ iEYEARECAAYFAk1jyuUACgkQ+gerLs4ltQ4SyQCgxmUkN5GdSZN/COkM/ETEc2CU 3FEAoJpArYj9aUJn7oYxORBXwc3IOQZp =nsJs -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] heads up about package moves...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/16/2011 05:09 AM, Danny Navarro wrote: I see that the repository mirrors for the different DVCS: git.repoze.org, bzr.repoze.bfg, hg.repoze.org are no longer maintained. The viewcvs also looks down, I don't remember the exact url though. Sorry about that. Those mirrors were casualties of January's hardware failure: getting them back up and working properly never got to the top of my list. I personally don't have a strong need for the mirrors, I only miss the commit feeds for certain packages that I was getting from bzr.repoze.org and also a nicer web interface to read code. What are the plans for repoze.org SVN? Are you thinking about moving them to github, too? Are there any plans to migrate them to another DVCS? We're chatting about that -- the most likely outcome at this point is that we will move the projects to github, perhaps under a repoze organization, but laid out in the same way (contributor agreements, etc.) 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/ iEYEARECAAYFAk1b6L0ACgkQ+gerLs4ltQ5y1QCfRvtDfI1Xu/8oSoenGk7IOECN I94AniBy7ZbIKoq8cimxNB5MoXDScGlE =9B5K -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue175] repoze.sphinx.autointerface generates exception if options.members is None
Tres Seaver tsea...@agendaless.com added the comment: Fix released: http://pypi.python.org/pypi/repoze.sphinx.autointerface/0.6.2 -- status: resolved - chatting __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue175 __ ___ 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 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
-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
[Repoze-dev] [issue174] repoze.who 2.0a3 doesn't respect the WSGI PEP
Tres Seaver tsea...@agendaless.com added the comment: Thanks for the report. -- status: unread - in-progress __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue174 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] Making Pyramid SQL authentication faster
on ug.group_id = g.id ... where u.id =13; sqlite - - % The callback would issue this query, and return None if the result set is empty. If the result set has a single record, and the 'g.name' value is Null, then the callback returns an empty sequence. Otherwise, the callback returns the sequence of group names in the result set. Something like:: - - % SQL = \ select g.name from users u left outer join user_groups ug on ug.user_id = u.id left outer join groups g on ug.group_id = g.id where u.id = % def callback(request, userid): dbconn = request.registry.settings['dbconn'] groups = [x.name for x in dbconn.execute(SQL, userid).fetchall()] if groups: if groups == [None]: return () return groups return None - - % I realize that many folks expect their ORM to do the SQL heavy lifting for them; unfortunately, I don't know any ORM well enough to suggest how to get this same effect. Note that this approach also sacrifices the convenience in the name of efficiency: a callback implemented this way doesn't make pre-populated user object available (or at least not easily). Summary - --- Cutting the number of SQL queries by half helps some. Doing more requires either changing the contract for the callback (mandating that it return only items which can safely be cached on the request) or else making the callback responsible for such caching. 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/ iEYEARECAAYFAk0mW18ACgkQ+gerLs4ltQ54xwCgoTY+ajtC0EF6u8Bo/Wt+WYnV BG4AnR6AVK+2SAhf/3zkUPKZ/91Avc7M =quiW -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] quick write up on precompiling chameleon zpt for appengine.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/17/2010 08:39 AM, Tim Hoffman wrote: Folks if any one is interested here is a quick writeup and sample code that precompiles chameleon zpt's for deployment on appengine. It is WIP. Comments, criticism welcome. http://code.google.com/p/bfg-pages/wiki/PrecompilingChameleonZPT Cool! Seems like your approach might be useful for folks wanting to run with PyPy or Jython as well (they still wouldn't be able to *develop* with Chameleon, but it's a start). 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/ iEYEARECAAYFAk0LjcoACgkQ+gerLs4ltQ5/KgCg2acCtJmZDlq5fWpFiDg1UP1f s+sAnjtYpaDz4MuM6J1ayuRwPKiV/mbj =SV9v -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] bfg chameleon unicode crash with wrapper views
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/15/2010 10:18 PM, Iain Duncan wrote:
Not sure where I'm supposed to ask this now, here? Pyramid list?
I have view with a chameleon template that contains utf-8 unicode special
chars. It renders fine when rendered on it's own from a view. As soon as I
wrap that view with a wrapper view, I get errors with the wrapper choking on
the unicode.
My master views call method is like this:
def __call__(self):
tmpl_dict = {}
tmpl_dict['inner_content'] = self.request.wrapped_body
return tmpl_dict
I get the following traceback ( snipped ):
File
/home/jordans/Jordans/eggs/repoze.bfg-1.2.2-py2.6.egg/repoze/bfg/router.py,
line 130, in __call__
response = view_callable(context, request)
File
/home/jordans/Jordans/eggs/repoze.bfg-1.2.2-py2.6.egg/repoze/bfg/configuration.py,
line 1724, in _owrapped_view
wrapper_viewname)
File
/home/jordans/Jordans/eggs/repoze.bfg-1.2.2-py2.6.egg/repoze/bfg/view.py,
line 90, in render_view_to_response
return view(context, request)
File
/home/jordans/Jordans/eggs/repoze.bfg-1.2.2-py2.6.egg/repoze/bfg/configuration.py,
line 1663, in _bfg_class_view
response = inst()
File /home/jordans/Jordans/jordans/views/master_view.py, line 22, in
__call__
tmpl_dict['inner_content'] = u%s % self.request.wrapped_body
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 4090:
ordinal not in range(128)
Any clues?
The code in the traceback doesn't match the sample you showed above:
the 'wrapped_body' is an encoded string (WebOb responses always encode
the body with the supplied charset) which the view is trying to decode
(back?) to unicode without supplying the encoding. The default encoding
used by WebOb is 'UTF-8', so I would try:
def __call__(self):
tmpl_dict = {}
body = self.request.wrapped_body
tmpl_dict['inner_content'] = body.decode('UTF-8')
return tmpl_dict
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/
iEYEARECAAYFAk0KGHEACgkQ+gerLs4ltQ7FZQCgzIl5cIsJbt1viMO8KKAre97j
ne8An1T4tFdxXHTQzOcSJyWpP7hGiBcq
=Ty1s
-END PGP SIGNATURE-
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue169] repoze.profile: useless profile recorded when application is a generator
Tres Seaver tsea...@agendaless.com added the comment: Fix released to PyPI: http://pypi.python.org/pypi/repoze.profile/1.2 -- status: chatting - resolved __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue169 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] repoze.what quickstart and the authtkt authenticator
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/23/2010 09:36 PM, Jim Hunziker wrote: Is there a reason why the AuthTktCookiePlugin isn't set up as an authenticator in the repoze.what quickstart? Adding it to authenticators in setup_sql_auth is the only way I can see being able to check permissions on a user who is on a page other than the login page. Likely that quickstart is designed for use with repoze.who 1.0.x, which had a (mis)feature called pre-authenticated credentials, now removed in repoze.who 2.0. At any rate, your fix is the correct one when moving to version 2.0 of reopze.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/ iEYEARECAAYFAkztAj4ACgkQ+gerLs4ltQ7UuACeJaimcwBtlzoeiW9n3Il08Guu Z9QAnRguFkV/mmx6SY3ZoehRzSbUtIli =jzou -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue169] repoze.profile: useless profile recorded when application is a generator
Tres Seaver tsea...@agendaless.com added the comment: Thanks for the report! I agree that your suggested solution is probably the correct one, with the exception that I would have it apply 'list()' only for results which were generators: hmm, how do I detect that? -- assignedto: - tseaver nosy: +tseaver status: unread - chatting __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue169 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue169] repoze.profile: useless profile recorded when application is a generator
Tres Seaver tsea...@agendaless.com added the comment: Fix checked in on the trunk for the next release. -- status: chatting - resolved __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue169 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue169] repoze.profile: useless profile recorded when application is a generator
Tres Seaver tsea...@agendaless.com added the comment: I just checked in a change which moves the conditional list inside the profiled code. Please give it a try. I made creation of the list condition in order to avoid injecting any unnecessary overhead into the profiled code. I'm probably being too fussy, but there you go. -- status: chatting - testing __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue169 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] basicauth plugin does not work with https/apache
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/15/2010 12:42 PM, cornelius wrote: Dear list, I am trying to do dual authentication. I am using repoze-who with pylons. (Due to my distribtion version 1.0.18 of repoze-who). I'd like to do form authentication when accessing a url with a browser and basic auth (or rather I'd use digest auth) when accessing with a API client. I followed the only description I could find by Chris Miles. It worked out fine so far. But I am serving my application through apache using mod_wsgi. AND I am using https, and unfortunately the basicauth.py plugin does not work for https. The 'HTTP_AUTHORIZATION': 'Basic hjksjhudsiuz', is not contained in the environ dictionary. Do you got any ideas for using https or even digest auth? I suspect I would have to write my own plugin for this (which would be ok for me, too) You need to tell mod_wsgi to include the auth headers: http://code.google.com/p/modwsgi/wiki/ConfigurationDirectives#WSGIPassAuthorization 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/ iEYEARECAAYFAkzhctgACgkQ+gerLs4ltQ6vGwCeITH0D8emYJRe4aR62GZqGqlG YlcAoK1j/6wSMTbOc/8eNOO23cYxFRep =tY0f -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] basicauth plugin does not work with https/apache
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/15/2010 02:17 PM, cornelius wrote: you made my day! Great. Just addind this, my configuration also works with digestAuth! What plugin are you using for digest authentication? 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/ iEYEARECAAYFAkzhiP4ACgkQ+gerLs4ltQ7zWwCeL51lEjqToUFU9zuTj2hstGXu QBEAoI9CCaDd9b4SwOE4ix5hEVgrn0Rx =SPCi -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] Chameleon and multiple select box
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/15/2010 08:29 PM, Uwe Hentzschel wrote: Hi I create a new project and add a multiple select box in mytemplate.pt. === % = /div /div /div div select multiple id=select1 option value=1Option 1/option option value=2Option 2/option option value=3Option 3/option option value=4Option 4/option /select a href=# id=addadd gt;gt;/a /div div id=footer div class=footer© Copyright 2008-2010, Agendaless Consulting./div /div === % = But I get an error: === % = File /Users/uhe/develop/pyramid-env/lib/python2.6/site-packages/Chameleon-1.2.13-py2.6.egg/chameleon/core/etree.py, line 102, in parse raise xml.parsers.expat.ExpatError(error_msg) RuntimeError: Caught exception rendering template. - Filename: /Users/uhe/develop/pyramid-env/demo/demo/templates/mytemplate.pt ExpatError: not well-formed (invalid token): line 77, column 24 === % = Chameleon requires valid XHTML in templates: in this case, the valueless 'multiple' attribute is the culprit (perfectly valid in HTML, but not XML). Spell it:: select multiple=multiple id=select1 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/ iEYEARECAAYFAkzh4KwACgkQ+gerLs4ltQ7fqQCgpq8q2JSiz4D7+O2y9OQZW0k9 KbIAni8287Fyvk2z9YRmvEq2eWLrqTRG =gNB6 -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] repoze.catalog clear
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/08/2010 10:04 AM, Tres Seaver wrote: On 11/08/2010 09:07 AM, Wichert Akkerman wrote: I have some code (from Chris) which rebuilds a repoze.catalog instance. It uses a very simple algorithm: catalog.clear() for each obj in root: index object if object is folderish: process al its children unfortunately there is one problem with this code: any stale items in catalog.document_map are not cleared, so there is still cruft remaining after rebuilding the catalog. Can that be considered to be a bug? Seems like a bug to me. Hmm, OTOH: one might use the un-cleared document map to rebuild the catalog indexes / metadata internally (rather than crawling the content space tree). The Zope2 catalog's Advanced tab does the moral equivalent of this operation. 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/ iEYEARECAAYFAkzYEe4ACgkQ+gerLs4ltQ7XzQCgjlIxCEkif0pyUdQ5VhcOqjZb vZEAn1mQPXaaswMc/TyrEtw6EmZoqJUi =2t2a -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] repoze.catalog clear
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/08/2010 10:10 AM, Wichert Akkerman wrote: On 11/8/10 16:09 , Chris Rossi wrote: The document_map, while sometimes stored on the catalog, is not known to the catalog. If you want to clear it, you need to do so explicitly. This is because r.catalog makes no assumptions about how you retrieve a document given a docid. The DocumentMap implementation is provided to fit a common case, but is still up to the app to manage. right. It would be nice if DocumentMap supported a clear() method though. The __init__ does what you want: def __init__(self): self.docid_to_address = IOBTree() self.address_to_docid = OIBTree() self.docid_to_metadata = IOBTree() Maybe you could just replace it? At any rate, I wouldn't object to renaming that method 'clear', and adding an '__init__' which called it. 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/ iEYEARECAAYFAkzYE/4ACgkQ+gerLs4ltQ65rwCdEgpNX0bDt7qm4WJPKzpCX41u rU0AniwOqy3eXKCrZQXXggKYoHT+Wc8u =HW9S -END PGP SIGNATURE- ___ 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
-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
Re: [Repoze-dev] enabling login with username or email + password
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/02/2010 03:32 PM, Ryan McKillen wrote:
I'm using the Quickstart plugin with Pyloins. My auth.py is pasted below.
I'm authenticating against a username filed in my database, but I'd like to
give users the option of logging in with their email address or username.
How can I add an additional authenticator to allow this? Thanks for the
help!
from repoze.what.plugins.quickstart import setup_sql_auth
from ubercab.model.meta import Session
from ubercab.model.user import User
from ubercab.model.authorization import Group, Permission
def add_auth(app, skip_authentication):
return setup_sql_auth(app, User, Group, Permission, Session,
skip_authentication = skip_authentication,
log_level = 'info',
login_url = '/login',
login_handler = '/authenticate',
post_login_url = '/dashboard',
logout_handler = '/logout',
post_logout_url = '/login',
cookie_secret = 'de9f2c7fd25e1b3afad3e85a0bd17d9b100db4b3',
translations = {
'user_name': 'username',
'group_name': 'name',
'permission_name': 'name'
}
)
I don't know anything about repoze.what.plugins.quickstart, but quick
browse of the sources indicates that you need to pass a custom
'form_plugin' to the 'setup_sql_auth' middleware factory. The default
if you don't pass one is to construct on instance of the FriendlyForm
plugin: in your case, I would probably derive my plugin from that
class, and pass in an instance of it.
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/
iEYEARECAAYFAkyocUkACgkQ+gerLs4ltQ4XZwCfQR8VHiiaYmpRyRYuKQQpnVST
5qsAn0Ve6K4nFgwfYZA3T4NZXhOzHqO+
=/7BG
-END PGP SIGNATURE-
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] repoze.who redirecting form plugin, and the use http response codes 302 vs 303
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tim Hoffman wrote: Hmm plot thickens Telstra seem to cache or set headers on pages from 302 and 303 to encourage the iphone/ipad to cache results of 302's and 303's. Maybe you need to add some 'Cache-Control' header to disable any caching then. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkyOXbIACgkQ+gerLs4ltQ4ROwCeLCY6oQD2Mk/GaOrbqPvsE4Xy G1cAoMGwchn+RHh/+JIGkgeuiIFTvtF2 =zOR2 -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] Colander i18n in deformdemo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Douglas Cerna wrote: I'm trying the deform demo and noticed in the Internationalization example (http://deformdemo.repoze.org/i18n/) that when I set the _LOCALE_ to russian, form controls and errors are in fact translated, but colander validation messages are not (for example I get a is not a number). I checked the colander egg and it has a 'ru' locale. Is there any way to make colander validation errors to be translated too? Hmm, it seems as though they should be translated: I would guess that either the templates for them don't include the correct 'i18n' stanzas, or else there aren't any translations in the .po file. Also, I translated deform and colander trunk messages to Spanish. Is there a chance or interest in them being included so I can send a patch? Sí, con much gusto. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkyJNKwACgkQ+gerLs4ltQ7ptgCg29XlakNkGbdrWjfNs7KxOFsC Ry0AnjKNuoJeFKRvza+f9cdguc1rhKDr =CN41 -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] Colander i18n in deformdemo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Douglas Cerna wrote:
--- On Thu, 9/9/10, Chris McDonough chr...@plope.com wrote:
No, it isn't a bug. The translation for that error
message (\${val}\ is not a number) doesn't exist in
the russian .po file, so it uses the default input.
All validation messages should work fine when actually
translated.
Confirmed. Sorry for the noise :)
I've attached the Spanish l10n patches for deform and colander trunks. I
guess you cannot put binary *.mo files in a patch, correct? :)
Also, I took the liberty of putting a Spanish link in the
Internationalization example. I hope that's ok.
Muchas gracias! I have applied your patches, and compiled the .mo files
myself.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkyJXbsACgkQ+gerLs4ltQ4ojACgnQpn3FvPu0eqN0Rsgf40cJB7
WxYAn2fPKzD5BSIQAgjdl7x2PIvPWlAq
=nu1k
-END PGP SIGNATURE-
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] repoze.bfg random intermittent server errors fetching static resources
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Iain Duncan wrote:
On Wed, Aug 18, 2010 at 4:28 PM, Chris Withers ch...@simplistix.co.ukwrote:
Iain Duncan wrote:
FWIW, I can sit there and hit reload, and get totally different responses
randomly, sometimes my bfg methods return what they are supposed to, and
others I get the 500s.
Could there be a connection with using resource directory overloads in the
zcml?
It would be good to see the exceptions that are logged on the server side
that match those 500s...
Chris
Here is the traceback from one of the times it screwed up. gah, I expect
this is not good for homestar runner, maybe something deeply wrong in my
model code?
The weird thing is now I just had no problem like 10 times in a row, and
other times the js app fails when it makes the same request (
/bookings/by_date/2010-08-18 ). But when I hit the same thing in the browser
or manually trigger the ajax code from the firebug console, it never fails.
Any clues to the meaning of this traceback are most appreciated.
16:37:01,938 INFO [irmacs.views.bookings] BookingView.by_date() date:
2009-12-18
Exception happened during processing of request from ('127.0.0.1', 38238)
Traceback (most recent call last):
File
/home/irmacs/irmacs_trunk/eggs/Paste-1.7.4-py2.6.egg/paste/httpserver.py,
line 1068, in process_request_in_thread
self.finish_request(request, client_address)
File /usr/lib/python2.6/SocketServer.py, line 320, in finish_request
self.RequestHandlerClass(request, client_address, self)
File /usr/lib/python2.6/SocketServer.py, line 615, in __init__
self.handle()
File
/home/irmacs/irmacs_trunk/eggs/Paste-1.7.4-py2.6.egg/paste/httpserver.py,
line 442, in handle
BaseHTTPRequestHandler.handle(self)
File /usr/lib/python2.6/BaseHTTPServer.py, line 329, in handle
self.handle_one_request()
File
/home/irmacs/irmacs_trunk/eggs/Paste-1.7.4-py2.6.egg/paste/httpserver.py,
line 437, in handle_one_request
self.wsgi_execute()
File
/home/irmacs/irmacs_trunk/eggs/Paste-1.7.4-py2.6.egg/paste/httpserver.py,
line 287, in wsgi_execute
self.wsgi_start_response)
File
/home/irmacs/irmacs_trunk/eggs/repoze.who-1.0.18-py2.6.egg/repoze/who/middleware.py,
line 107, in __call__
app_iter = app(environ, wrapper.wrap_start_response)
File
/home/irmacs/irmacs_trunk/eggs/repoze.bfg-1.2.1-py2.6.egg/repoze/bfg/router.py,
line 130, in __call__
response = view_callable(context, request)
File
/home/irmacs/irmacs_trunk/eggs/repoze.bfg-1.2.1-py2.6.egg/repoze/bfg/configuration.py,
line 1665, in _bfg_class_view
response = getattr(inst, attr)()
File /home/irmacs/irmacs_trunk/Irmacs/irmacs/views/bookings.py, line 47,
in by_date
bookings = self.model.list( Booking, {'date':isodate} )
File
/home/irmacs/irmacs_trunk/framework_src/xornot.model/xornot/model/__init__.py,
line 208, in list
items = query.all()
File
/home/irmacs/irmacs_trunk/eggs/SQLAlchemy-0.5.8-py2.6.egg/sqlalchemy/orm/query.py,
line 1267, in all
return list(self)
File
/home/irmacs/irmacs_trunk/eggs/SQLAlchemy-0.5.8-py2.6.egg/sqlalchemy/orm/query.py,
line 1422, in instances
rows = [process[0](context, row) for row in fetch]
File
/home/irmacs/irmacs_trunk/eggs/SQLAlchemy-0.5.8-py2.6.egg/sqlalchemy/orm/query.py,
line 2032, in main
return _instance(row, None)
File
/home/irmacs/irmacs_trunk/eggs/SQLAlchemy-0.5.8-py2.6.egg/sqlalchemy/orm/mapper.py,
line 1751, in _instance
state._run_on_load(instance)
File
/home/irmacs/irmacs_trunk/eggs/SQLAlchemy-0.5.8-py2.6.egg/sqlalchemy/orm/state.py,
line 119, in _run_on_load
self.manager.events.run('on_load', instance)
AttributeError: 'NoneType' object has no attribute 'run'
This traceback is clearly not from a request serving a static resource:
you are seeing a bug (maybe a race condition due to use of globals?) in
your application.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkxtIJwACgkQ+gerLs4ltQ6JewCfbc9vS/ILlZ7miiDpcXvlOh2m
MzUAn3TPQpeYRsQMHJyU05G3ES6wmjuv
=mPcE
-END PGP SIGNATURE-
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue155] Support encoding of cookies on repoze.who cookie plugin
Tres Seaver tsea...@agendaless.com added the comment: The patch looks reasonable, but needs test coverage. Can you add tests for the encoding / decoding code paths? -- nosy: +tseaver status: unread - chatting __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue155 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] Problem with BFG on jython
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris McDonough wrote:
On Thu, 2010-07-01 at 23:02 -0500, Eduardo Diaz wrote:
I'm trying to use the latest version of repoze.bfg.jinja2 (0.6) on
jython, when trying to build it I get the following error:
building 'zope.i18nmessageid._zope_i18nmessageid_message' extension
error: Compiling extensions is not supported on Jython
I think someone may have fixed zope.i1n8nmessageid recently, causing
this problem. Can you try to install the older 3.5.0 version of
zope.i18nmessageid before installing repoze.bfg.jinja2 (e.g.
easy_install zope.i18nmessageid==3.5.0) and see if installing r.b.jinja2
works then. If so, I'll need to figure out how to re-unfix
zope.i18nmessageid. ;-)
The 'codeoptimizations' feature constructor can take an 'available'
argument which could be false, e.g.:
- --- % --
CANNOT_COMPILE = [
'java',
]
codeoptimization = Feature(Optional code optimizations,
standard=True,
available=os.name not in CANNOT_COMIPLE,
ext_modules=[
Extension(zope.i18nmessageid._zope_i18nmessageid_message, [
os.path.join('src', 'zope', 'i18nmessageid',
_zope_i18nmessageid_message.c)
]),
],
)
- --- % --
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkwt/coACgkQ+gerLs4ltQ6qlACcCVlLYbCIKEf4DCI3AIYQ1Vhj
upYAni5PqGy6ToCONvkDVqfyw5gQRZaW
=30CC
-END PGP SIGNATURE-
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] repoze.zodbconn connection handling
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Shane Hathaway wrote: On 06/25/2010 12:03 PM, Wichert Akkerman wrote: I am using repoze.zodbconn in a BFG application but I suspect it is not working as it should be: as soon as multiple requests come in at the same time I get a lot of locking errors and broken results: LockError: Couldn't lock '/Users/wichert/Work/code/buildout/blackbox/var/Data.fs.lock' The way I've setup repoze.zodbconn is from repoze.zodbconn.finder import PersistentApplicationFinder from myproject import appmaker finder = PersistentApplicationFinder(settings[zodb.url], appmaker) def get_root(request): return finder(request.environ) return get_root According to the docs[1], your code should look more like this: from repoze.zodbconn.finder import PersistentApplicationFinder from myproject import appmaker finder = PersistentApplicationFinder(settings[zodb.url], appmaker) app = finder(request.environ) return app OTOH, personally, I don't think this is a good pattern. I think the right idea is to open the connection in the WSGI stack [2]. That way, other WSGI components can use the connection, and you can guarantee that the connection gets closed. repoze.zodbconn supports both patterns. Could we make your preferred pattern lazier? E.g., instead of opening the connection and stashing it in the environ, could we stash an opener function, which would then be called by the API used by the app to extract the connection from the environ. That function could arrange to have the closer written back into the environ for the egress-side zodbconn middleware to use, for instance. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkwlB0sACgkQ+gerLs4ltQ5MFACgmZtNQP1nhXR/Cwcg+WjR8qb5 sbIAoLODPOVTmXJDpoRPKmqxvFk/F+7k =nD9V -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] repoze.zodbconn connection handling
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Shane Hathaway wrote: On 06/25/2010 01:16 PM, Chris McDonough wrote: We've addressed this in repoze.who by giving r.who's middleware a mode which injects only a factory into the environ instead of more eagerly constructing identity information. We can't really do that for repoze.zodbconn#connector, or at least it doesn't make much sense to do so, given that the entire purpose of opening it early is to be able to close it easily. You brought up a good point. Why couldn't we apply the same pattern here? The connector middleware could look something like this: class ConnectionFactory: def __init__(self, db): self.db = db self.connection = None def __call__(self): if self.connection is None: self.connection = self.db.open() return self.connection def close(self): if self.connection is not None: self.connection.close() class ConnectionMiddleware: def __init__(self, next_app, db): self.next_app = next_app self.db = db def __call__(self, environ, start_response): factory = ConnectionFactory(self.db) self.environ['repoze.zodbconn.connection_factory'] = factory try: return self.next_app(environ, start_response) finally: factory.close() Then we could make PersistentApplicationFinder use 'repoze.zodbconn.connection_factory' from the environment. That looks lazy enough for my taste. ;) Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkwlClUACgkQ+gerLs4ltQ54ZACgmgZR+Q1qp7YeyMCsMPue40zC bl0An06+EJMmj3XPcVrxNw7y6P2JGAbL =8Fml -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] repoze.org doesn't seem to be responding (at least from Australia)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Charlie Clark wrote: Am 23.05.2010, 11:28 Uhr, schrieb Tim Hoffman zutes...@gmail.com: Hi Subject says it all.. Anyone else experience it or is it just me Invisible here as well. Maybe they've installed Plone? ;-) I have asked the hosting service to reboot the machine, after their self-help reboot didn't work. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkv5II8ACgkQ+gerLs4ltQ4xeACgqPk6Xe1XYf3xecgHUjL+xyi9 +sUAoKyZ5dkKfhDkcxTOCelOkNObjzHz =y1Xm -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] Multiple authentication methods
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Roland Hedberg wrote: I have a use case where I would like the user to chose which authentication method to use. It's easy to have serveral authentication methods in repoze.who. But the normal case is that they are tried in order until someone succeeds or all are tried. I'd like the user to be presented with a set of choices and then use the one choosen. Is this be possible to do ? Not really: you would have to fake an authentication plugin which sniffed the request environment for that choice and delegated to other plugins: likely the fake would be the only one registered directly with repoze.who as an authentication plugin. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvoCsQACgkQ+gerLs4ltQ6XBQCbBuKaRGc5cIYLgG/ly7mqqjD0 ul4An2C29bVL89bbEpHl1sPP2q5p39q3 =Kv5c -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] How can I launch only one test with python setup.py test ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 KLEIN Stéphane wrote: Hi, usually I use nose to execute my tests. In Chameleon project, I can't use nose, example of fail : (env1)$ nosetests src/chameleon/tests/test_doctests -vs Failure: OSError (No such file /home/harobed/projets/repoze/chameleon/src/chameleon/src/chameleon/tests/test_doctests) ... ERROR == ERROR: Failure: OSError (No such file /home/harobed/projets/repoze/chameleon/src/chameleon/src/chameleon/tests/test_doctests) -- Traceback (most recent call last): File /home/harobed/projets/repoze/env1/lib/python2.6/site-packages/nose/failure.py, line 39, in runTest raise self.exc_class(self.exc_val) OSError: No such file /home/harobed/projets/repoze/chameleon/src/chameleon/src/chameleon/tests/test_doctests -- Ran 1 test in 0.001s FAILED (errors=1) Well, I can use ``python setup.py test`` to launch all tests. Question : * how can I launch only one test, example ``chameleon/tests/test_doctests.py:CoreTests.test_parsing_module`` ? Thanks for your help, Try running 'python setup.py --help' to see the options you can pass on the command line. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvcXEsACgkQ+gerLs4ltQ6KqACgz2kdvY6gorlQsj+Z5/uDD5xp /3kAn3oySYSMCfQcvE2Gh5pEnduPvhGI =VEGe -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] SAML2 in repoze.who
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Roland Hedberg wrote: I just released PySAML2 on Pypi. It's a SAML2.0 implementation intended for use within a WSGI frameworks. When I developed it I used repoze.who as the WSGI framework. Any comments are appreciated. This looks really cool! I've been working on getting the big picture docs together for repoze.who 2.0, and your plugin fits into that nicely: validates the architecture, actually. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvaTxYACgkQ+gerLs4ltQ5PjQCgrbSE9FCFMoo32QIubfp+b+ou xtEAoIrue/23oKsqn/h7UwIH80AFqJYj =M6jm -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] urlparse patch for repoze.zodbconn
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Fergus Doyle wrote: Apologies, the patch was the wrong way round Thanks for the patch! Now released in repoze.zodbconn 0.11: http://pypi.python.org/pypi/repoze.zodbconn/0.11 Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvV2IYACgkQ+gerLs4ltQ5+qQCfUQXJbLXbGCpc4tH3/+8w130f rIAAoIYIHrWk6Nwu8BYfKXMeR/DnuYlX =Nour -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue100] Configurable character set support for repoze.who and repoze.what
Tres Seaver tsea...@agendaless.com added the comment: The only correct way to decode values in the payload of an HTTP POST request is to use the charset supplied in the Content-Type header of that request, or fall back to ISO-8859-1. RFC 2616, section 3.7.1, says: When no explicit charset parameter is provided by the sender, media subtypes of the text type are defined to have a default charset value of ISO-8859-1 when received via HTTP. -- status: resolved - chatting __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue100 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue114] Documentation error
Tres Seaver tsea...@agendaless.com added the comment: Thanks very much for the report! Fixed on the trunk in r9049. Fixed on the 1.0 branch in 9050. -- status: chatting - resolved __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue114 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue41] INITools for zc.buildout-style config files
Tres Seaver tsea...@agendaless.com added the comment: Looks interesting. I'm not sure I'd want to document how to use the feature, though. ;) -- priority: feature - wish status: unread - chatting __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue41 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue111] repoze.who.plugins.ldap enhancements
Tres Seaver tsea...@agendaless.com added the comment: That plugin tracks its bugs in Launchpad: https://bugs.launchpad.net/repoze.who.plugins.ldap -- status: unread - chatting __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue111 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue41] INITools for zc.buildout-style config files
Tres Seaver tsea...@agendaless.com added the comment: That code now lives at BitBucket: http://bitbucket.org/ianb/initools/ __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue41 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
