I am a !#4@head ;-)
Hi FolksThis is a quick and dirty change and to be honest the main reason I am posting it here is so there is a searchable recordfor anyone else who wants to use zope.deferredimport under google app engine. (With some content modelszope.deferredimport is a great way of dealing with cyclic dependancies and possibly improving startup times - see bottom of this email.)Below is a minimal set of changes to zope.proxy.__init__ that is required so that zope.deferredimport can be used.It does mean you need peak.utils to implement a basic proxy.
There are a couple of other zope.proxy functions from the 'c' api that I haven't looked at yet as they aren't used by zope.deferredimport.Suggestions on improving it and/or followups on the other functions would also be welcome. I have also found that deferred import can helpwith app engine startup times as it means you can import a module you depend on but not really import the code until it gets touchedwhich can allow you to stagger you startup costs. (For instance edit functionality of a site could be deferred until someoneactually edits something).Hope this helps someoneRegardsTim Hoffman