Howdy Jason, things are going pretty well, castle sprinting at the moment post plone conference.
regarding the patch, its completely transparent to use, ie. if you weren't using explicit transaction management before, you'll get them for free without any changes to your app code. transaction boundaries are setup for the start and end of a web request ( ala zope ), freeing the app programmer from thinking about it unless they need more advanced functionality. the dependencies can be made much smaller, i talked to jim fulton earlier today about this patch, as it is definitely a goal of z3 to be able to use it as a normal python library, and what can be done to scale down the dependencies for it. with a little work the, dependencies can be mitigated down to 3 packages ( transaction, zope.interface [ which also brings in adapter machinery ], and zope.rdb [ moved up from zope.app.rdb ] ). the zope interface package is already in use by a few external projects, twisted coming immediately to mind. the real question to me though, is there interest in integrating transaction management by the django developers, and if the sort of integration i've done is the 'right' way to go about it. cheers, kapil
