Been working on Zope 3 Security for the last few days, and I must say
its quite pluggable, and easy to debug, except that now I found a
show-stopper which I can’t really tell if it’s a problem with my
interpretation of the security machinery, or if it’s really something
that has to be fixed.

About pluggability, I’ve been able to write an adapter to save the
roles->principal mappings in SQL, using SQLObject. My approach is not
the best one, as I’m using the path as part of the key for finding the
settings. The optimal version would generate a unique key on a table
instead, and I plan to implement that sometime soon.

For debugging, there is a nice hack inside
zope/security/checker.py that reports failures to the stdout when
you set an environment variable named ZOPE_WATCH_CHECKERS. So, you
see the fun? I’ve been watching checkers for days!

From WordNet (r) 2.0 [wn]:

checkers

n : a checkerboard game for two players who each have 12
pieces; the object is to jump over and so capture the opponent’s
pieces [syn: {draughts}]

I’m packing up stuff for my trip to Sao Carlos next Wed. Already
bought the tickets, and a backpack, so that sums up to 3 items cleared
from my TODO, and a couple more that weren’t there but I finished in
the meantime.

Finished my article about Archetypes for the ZopeMag, which is
going to be published in Issue 06. Many thanks for publishing it. Hail Mark!

So, this Wed I’m leaving to Sao Carlos and back on the Tue, right in
time for exams. IIRC!