I'm trying to port zope.proxy to Python 3, and most tests seem to
work, but investigating those two who doesn't is confusing. The first
one is the test to prevent pickling. This works under Python 2, but as
I understand it it should work by implementing a __reduce__ function
that throws an
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
Hi,
Is there any documentation on zope.proxy other than the test? I don't
speak C anymore. :)
Basically, I'm curious if it would be possible to implement translation
proxies that would allow getting and setting translated values for
certain fields.
Cheers,
Martin
--
Author of `Professional
Martin Aspeli wrote:
Is there any documentation on zope.proxy other than the test? I don't
speak C anymore. :)
I find ``zope.location.location.LocationProxy`` to be a good example of
its usage.
\malthe
___
Zope-Dev maillist - Zope-Dev@zope.org
Hi there,
On Fri, 2009-06-26 at 18:30 +0800, Martin Aspeli wrote:
Hi,
Is there any documentation on zope.proxy other than the test? I don't
speak C anymore. :)
Basically, I'm curious if it would be possible to implement translation
proxies that would allow getting and setting
Hi Christian,
Thanks for this!
Have a look at the attached file, it contains the code that I extracted
from a project in a hurry, but if the approach sounds reasonable to you,
I'd be happy to put that into SVN.
Can you tell me a bit more about how this is hooked into publication?
Where do
