$ svn co http://svn.repoze.org/buildouts/repoze.plone/branches/2.5.5 $ cd 2.5.5 $ python2.4 bootstrap.py $ bin/buildout .. follow instructions here on in ..

$ virtualenv24 --no-site-packages plone255 $ cd plone255 $ bin/easy_install -i http://dist.repoze.org/plone/2.5.5/simple repoze.plone $ bin/mkzope2instance . $ bin/addzope2user admin admin $ bin/paster serve etc/zope2.ini

$ svn co http://svn.repoze.org/buildouts/repoze.zope2/branches/2.9 $ cd 2.9 $ python2.4 bootstrap.py $ bin/buildout .. follow instructions here on in ..

$ virtualenv24 --no-site-packages zope298 $ cd zope298 $ bin/easy_install -i http://dist.repoze.org/zope2/2.9/simple repoze.zope2 $ bin/mkzope2instance . $ bin/addzope2user admin admin $ bin/paster serve etc/zope2.ini

One good thing about doing this work is that it's becoming a little clearer how we need to lay out our distribution site (dist.repoze.org) to support multiple build revisions of the same piece of software. I haven't managed yet to clean it up entirely but I think I know how to now.

Have fun!

-C ]]> Repoze Notes 2008-05-07T17:53:00Z http://www.stereoplex.com/two-voices/creating-a-python-2-4-plone-and-zope-development-environment-on-mac-os-x-leopard Stereoplex 2008-05-07T15:51:41Z http://tarekziade.wordpress.com/2008/05/07/pycon-fr-is-coming-up-ask-the-program/ conference plone pycon python zope Carpet Python zope 2008-05-07T12:34:37Z http://plone.org/news/plone-symposium-early-bird-registration-extended Plone News 2008-05-06T21:48:42Z http://martinaspeli.net/articles/update-repoze-under-mod-wsgi-is-not-slow Martin Aspeli 2008-05-06T21:43:20Z http://www.zeapartners.org/articles/plone-it001 Zea Partners News 2008-05-06T12:17:47Z http://tarekziade.wordpress.com/2008/05/06/plone-paris-sprint-wrapup-3-newploneorg-collectivedist-released/ plone python sprint zope distutils zc.buildout Carpet Python zope 2008-05-06T11:50:15Z http://blog.ianbicking.org/2008/05/05/choosing-a-license/ Programming Ian Bicking: a blog 2008-05-05T22:48:48Z http://blog.repoze.org/optilude-rolling-out-repoze.html Repoze Notes 2008-05-04T17:17:00Z http://martinaspeli.net/articles/rolling-out-repoze Martin Aspeli 2008-05-04T17:13:00Z http://blog.repoze.org/repozewho-1.0.html

Version 1.0 has optional support for middleware configuration via a config file (thanks to Tres). Being a framework, is configuration-heavy, and it can provide a better separation of concerns and more convenience to wire it up via a configuration file than via Python code. So rather than configuring the middleware and attendant plugins via straight Python code, you can now wire who configuration up in an .ini file:

# who.ini

[plugin:form] # identification and challenge use = repoze.who.plugins.form:make_plugin login_form_qs = __do_login rememberer_name = cookie form = %(here)s/login_form.html

[plugin:auth_tkt] # identification use = repoze.who.plugins.auth_tkt:make_plugin secret = s33kr1t cookie_name = oatmeal secure = False include_ip = False

[plugin:basicauth] # identification and challenge use = repoze.who.plugins.basicauth:make_plugin realm = 'sample'

[plugin:htpasswd] # authentication use = repoze.who.plugins.htpasswd:make_plugin filename = %(here)s/passwd check_fn = repoze.who.plugins.htpasswd:crypt_check

[plugin:sqlusers] # authentication use = repoze.who.plugins.sql:make_authenticator_plugin query = "SELECT userid, password FROM users where login = %(login)s;" conn_factory = repoze.who.plugins.sql:make_psycopg_conn_factory compare_fn = repoze.who.plugins.sql:default_password_compare

[plugin:sqlproperties] name = properties use = repoze.who.plugins.sql:make_metadata_plugin query = "SELECT firstname, lastname FROM users where userid = %(__userid)s;" filter = my.package:filter_propmd conn_factory = repoze.who.plugins.sql:make_psycopg_conn_factory

[general] request_classifier = repoze.who.classifiers:default_request_classifier challenge_decider = repoze.who.classifiers:default_challenge_decider

[identifiers] # plugin_name;classifier_name:.. or just plugin_name (good for any) plugins = form;browser auth_tkt basicauth

[authenticators] # plugin_name;classifier_name.. or just plugin_name (good for any) plugins = htpasswd sqlusers

[challengers] # plugin_name;classifier_name:.. or just plugin_name (good for any) plugins = form;browser basicauth

[mdproviders] plugins = sqlproperties

Then you can use a constructor to create the configuration based on the .ini file, e.g.:

from repoze.who.config import WhoConfig

app = {next app in pipeline} here = os.path.dirname(__file__) config_file = os.path.join(here, 'who.ini') parser = WhoConfig(here) parser.parse(open(config_file)) middleware = PluggableAuthenticationMiddleware(app, parser.identifiers, parser.authenticators, parser.challengers, parser.mdproviders, parser.request_classifier, parser_challenge_decider, log_stream = sys.stdout, log_level = logging.DEBUG, )

There is a PasteScript-compatible constructor available via the egg name that does just this, so you can also just wire it up via a paste config file equivalently, ala:

[filter:who] use = egg:repoze.who#config config_file = %(here)s/etc/who.ini log_level = debug log_stream = stdout

for more information about configuration. ]]> Repoze Notes 2008-05-04T14:52:00Z http://maurits.vanrees.org/weblog/archive/2008/05/grok-sprint-wrapup-sunday

Philipp released grokcore.component and merged the needed changes to core grok.

A lot of documentation was written. Automation is done using grokdocs.

JW and Philipp worked on martian directives. Three merges need to happen, which we will work on now. Makes it easier to write new directives and easier to get information from directives. All existing third party grokkers will then not more work anymore; we feel it is still early enough to do this, but the merge should happen sooner rather than later. ]]> grok plone Weblog 2008-05-04T13:43:53Z