A well-written open letter to the Django development community on the practices which make a setuptools-based development process go more smoothly than the historical experience which soured that community on the idea.
A really nicely-done presentation analyzing the costs and tradeoffs of the "monolithic" development culture of Zope2, and recommendations for avoiding the pitfalls.
http://www.youtube.com/watch?v=fipFKyW2FA4&feature=PlayList&p=D415FAF806EC47A1&index=12
Notes on work done and proposed during the sprint, 12 - 14 September 2008.
In a straight setupttools-based application, adding one or more
console scripts is straightforward: you just declare them in the
setup.py, and set setuptools build them for you. However, when
using zc.buildout for Plone 3.0.x or 3.1.x, you have to arrange to
get the non-eggified Zope2 products on the path, which is not easy.
This recipe works for me.
I blogged yesterday about the fact that I had docs online
for the repoze.urispace package, but didn't do much to motivate
readers' interest: repoze.urispace should be interesting if you have
an application which needs policies which vary based on "where" in
the site the request is addressed. Examples might include: fine-
grained security, theme selection, caching policies, etc.
I have uploaded Sphinxified documentation for repoze.urispace, a
library package which implements most of the W3C URISpace spec
for use in WSGI middleware. I'm planning to use it to select
themes and rulesets for Deliverance based on the URI; other uses
might include setting caching headers, or doing some flavor of
"declarative security" in middleware.
The goals of the kind of testing outlined here are simplicity, loose or no coupling, and speed:
Developers write such tests to verify that the AUT is abiding by the contracts the developer specifies. While an instance this type of test case may be illustrative of the contract it tests, such test cases do not take the place of either API documentation or of narrative / "theory of operations" documentation. Still less are they intended for end-user documentation.
Looking back at ten years of programming web applications with Python, and musings on what lies ahead.
I just uploaded version 0.1 of a new product to the Cheeseshop. It provides partial GenericSetup support for the tools present in a Plone 2.5.x site.
http://pypi.python.org/pypi/Products.plone_gs/0.1
I will be tracking issues against the product at http://agendaless.com/home/tseaver/software/plone_gs/issues
A brief proposal on how and when one might prefer to use "standard"
setuptools features, rather than relying on zc.buildout.