Re: Optional C extensions
Jim Fulton <[email protected]>
| Newsgroups | gmane.comp.web.zope.devel |
|---|---|
| Message-ID | <[email protected]> |
On Tue, Mar 9, 2010 at 6:15 PM, Tim Hoffman <[email protected]> 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 can use zope.deferredimport on app engine. > > Below is the awful hacking I do to zope.proxy.__init__ to make it > support zope.deferredimport on appengine. Please don't encourage this. People reading this, please forget you read Tim's email. :) (Jim whips out special pen and asks that everyone look in his direction for a moement.) zope.deferred import should, perhaps, be modified to use peak.util.proxies, but we should not have packages floating around that modify zope.proxy to weaken it. I wish I had agitated to make changes to Python to make deferred imports use of zope.proxy unnecessary. Jim -- Jim Fulton _______________________________________________ Zope-Dev maillist - [email protected] https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )