Hi,
I'm trying to work out why the following code is in the bfg_alchemy
template
(http://repoze.org/viewcvs/repoze.bfg/trunk/repoze/bfg/paster_templates/alchemy):
subscriber for=repoze.bfg.interfaces.INewRequest
handler=.run.handle_teardown
/
def handle_teardown(event):
environ
2010/4/29 Chris McDonough chr...@plope.com:
On 04/29/2010 10:39 AM, Chris Withers wrote:
Chris McDonough wrote:
As far as I know this is unnecessary. It's not in the repoze.cluegun
app, nor in the app I worked on at Jarn. Are there any problems when
you remove it?
No idea. Withers, can
On 2 May 2010 22:03, Luciano Ramalho luci...@ramalho.org wrote:
In these, we don't store serialized objects, but just the data to
reconstruct the objects. But the data is not completely dismembered in
some normalized form.
In a semi-structured database the data graph can follow very closely
On 4 May 2010 18:46, Charlie Clark charlie.cl...@clark-consulting.eu wrote:
Am 04.05.2010, 19:20 Uhr, schrieb Laurence Rowe l...@lrowe.co.uk:
I suspect that databases such as CouchDB and the others you mention
are not well suited to graph traversal. Efficient traversal must occur
near
I've made a repoze.xmliter 0.2 release at
http://pypi.python.org/pypi/repoze.xmliter/0.2 with the following
changes:
0.2 - 2010-09-11
* Use document encoding by default. (This fixes test failure on Ubuntu 10.04.)
* Defer to xsl:output settings when serializing an XSLResultTree.
An auth_tkt cookie also has space to store 'tokens', i.e. groups or
roles and 'user data', which might be used for storing fullname and
email address. Obviously there is a trade-off to be made between
cacheabiliy and liveness, but for many sites I suspect all of this
data could be safely set on a
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
