[Zope-dev] Acquisition wrapped objects do not behave well on unicode call
Christian Zagrodnick
cz at gocept.com
Wed Feb 16 16:19:00 EST 2011
On 2011-02-16 10:10:05 +0100, Hanno Schlichting said:
> On Wed, Feb 16, 2011 at 9:18 AM, Michael Howitz <mh at gocept.com> wrote:
>> Zope 2.12.8 on Python 2.6 breaks the same way as 2.13.
>> But Zope 2.11.7 on Python 2.5 works correctly.
>>
>> So either Python or Acquisition must have changed since than.
>
> Acquisition changed a lot from 2.11 to 2.12 - it got support for
> parent pointers for example. The full changelog is quite long, but
> should be unrelated
> (http://pypi.python.org/pypi/Acquisition#changelog).
>
> The full diff is at:
>
> svn di
> svn+ssh://svn.zope.org/repos/main/Acquisition/branches/2.11/src/Acquisition/_Acquisition.c
svn+ssh://svn.zope.org/repos/main/Acquisition/trunk/src/Acquisition/_Acquisition.c
There's
>
> nothing obvious I can see here.
I suspect a change in python (which I did not follow up after getting
strange feelings when looking at PyObject_Unicode).
Nevertheless I've fixed that on a branch:
svn+ssh://svn.zope.org/repos/main/Acquisition/branches/zagy-unicode-should-be-called
Hanno:
Would you review that change please?
Thanks.
--
Christian Zagrodnick · cz at gocept.com
gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany
http://gocept.com · tel +49 345 1229889 4 · fax +49 345 1229889 1
Zope and Plone consulting and development
More information about the Zope-Dev
mailing list