Hi Jens I have attached a hacked zope.proxy and peak.utils which implements the proxy. I used this a while back when I got plain zope3 going on gae. Now that i am using repoze.bfg on gae I haven't had to use it but it might help you I have found I am also not using zope.location (repoze.bfg has some alternatives) which could be another way of getting around the problem. Also if you run into problems with zope.security give me a yell as I have a hacked zope.deferredimport and zope.security I can shoot your way I personally have also stopped using these because I have all I need in bfg at the moment and I think all the refactoring going on in zope3 (ZTK) will probably be a much more supported direction compared with my ugly hacks from last year ;-) T On Thu, Jul 9, 2009 at 1:54 AM, Jens W. Klein <jens@bluedynamics.com> wrote:
Hi, I'am just playing with repoze.bfg in google appengine (gae) and stumbled over zope.proxy. I tried to use zodict.node.Node which depends on zope.location. zope.location depends on zope.proxy. Latter has mandatory C-extensions. Are there any plans to get rid of them as a fallback for those spezial cases like gae? For zope.interface it was possible too ...
tia -- Jens W. Klein - Klein & Partner KEG - BlueDynamics Alliance
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )