Hi,
here's the summary of yesterday's meeting. The meeting itself was going
more in-depth on the topic we covered so for the next meeting I'll make
the agenda even shorter.
On the experiment side: while writing up the summary I noticed that
yesterday's discussions started going into different
Summary of messages to the zope-tests list.
Period Tue Mar 9 12:00:00 2010 UTC to Wed Mar 10 12:00:00 2010 UTC.
There were 6 messages: 6 from Zope Tests.
Tests passed OK
---
Subject: OK : Zope-2.10 Python-2.4.6 : Linux
From: Zope Tests
Date: Tue Mar 9 20:36:32 EST 2010
URL:
On Tue, Mar 9, 2010 at 6:15 PM, Tim Hoffman zutes...@gmail.com wrote:
Hi
As Attila pointed out, zope.proxy is possible to implement using
peak.util.proxies
if you only want some limited zope.proxy support. You won't get
zope.security going down
this path.
I do that specifically so that I
Hi Jim
Yeah I agree with you.
I haven't ever distributed that version of zope.proxy , just used it
internally to support deferredimport.
zope.security could never to what it does with a pure python version
of zope.proxy. the 'c' wrappers are very important to ensure security.
Unfortunately I
On Wed, Mar 10, 2010 at 7:17 AM, Tim Hoffman zutes...@gmail.com wrote:
...
Unfortunately I needed deferredimport and was completely unsure how
else to proceed at the time.
I use code generation for gae based models, and the unfortunately
reference entities need actual models/classes which
