Re: [Zope-dev] Acquisition wrapped objects do not behave well on unicode call

2011-02-16 Thread Michael Howitz
Am 15.02.2011 um 14:35 schrieb Michael Howitz: [...] print unicode(a.__of__(app)) __str__ called [...] This happens for Python 2.6 and 2.7 on Zope 2.13.4. 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

Re: [Zope-dev] Acquisition wrapped objects do not behave well on unicode call

2011-02-16 Thread Hanno Schlichting
On Wed, Feb 16, 2011 at 9:18 AM, Michael Howitz m...@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

Re: [Zope-dev] zope.contentprovider not useable together with Zope 2.13.4

2011-02-16 Thread Sylvain Viollon
On Tue, 15 Feb 2011 14:46:11 +0100 Michael Howitz m...@gocept.com wrote: Hi, Hello, we are upgrading a customers project from Zope 2.11.x to Zope 2.13.4. In this project the expression type provider of zope.contenttype is used. But loading the configure.zcml of zope.contentprovider fails

[Zope-dev] zope.[testing.]testrunner does not handle unexpected successes correctly

2011-02-16 Thread Michael Howitz
Hi, Python 2.7 added the concept of expectedFailures to unittest. See http://www.voidspace.org.uk/python/articles/unittest2.shtml#more-skipping When a test decorated with @unittest.expectedFailure does not raise an exception, this test is counted as success when running the tests with

[Zope-dev] Zope Tests: 64 OK, 23 Failed, 2 Unknown

2011-02-16 Thread Zope Tests Summarizer
Summary of messages to the zope-tests list. Period Tue Feb 15 12:00:00 2011 UTC to Wed Feb 16 12:00:00 2011 UTC. There were 89 messages: 8 from Zope Tests, 4 from buildbot at pov.lt, 33 from buildbot at winbot.zope.org, 11 from ccomb at free.fr, 33 from jdriessen at thehealthagency.com. Test

Re: [Zope-dev] Sprints at PyCon

2011-02-16 Thread Christian Theune
On 02/10/2011 07:38 AM, Baiju M wrote: Hi Theune, On Thu, Feb 10, 2011 at 11:58 AM, Baiju Mbaiju.m.m...@gmail.com wrote: On Thu, Feb 10, 2011 at 11:37 AM, Christian Theunec...@gocept.com wrote: Hi, I'll be at PyCon during the sprints. As promised from the tasks last year, I'd be happy to

Re: [Zope-dev] Zope Tests: 64 OK, 23 Failed, 2 Unknown

2011-02-16 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/16/2011 06:58 AM, Zope Tests Summarizer wrote: Subject: FAILED : winbot / zope.copypastemove_py_265_32 From: buildbot at winbot.zope.org Date: Tue Feb 15 11:10:48 EST 2011 URL:

Re: [Zope-dev] Zope Tests: 64 OK, 23 Failed, 2 Unknown

2011-02-16 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/16/2011 10:54 AM, Tres Seaver wrote: Hmmm, what is this 'zope.configure' thing? --- % -- Couldn't find index page for 'zope.configure' (maybe misspelled?) Getting distribution for

Re: [Zope-dev] Acquisition wrapped objects do not behave well on unicode call

2011-02-16 Thread Christian Zagrodnick
On 2011-02-16 10:10:05 +0100, Hanno Schlichting said: On Wed, Feb 16, 2011 at 9:18 AM, Michael Howitz m...@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.

Re: [Zope-dev] Acquisition wrapped objects do not behave well on unicode call

2011-02-16 Thread Hanno Schlichting
On Wed, Feb 16, 2011 at 10:19 PM, Christian Zagrodnick c...@gocept.com wrote: 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:

Re: [Zope-dev] Acquisition wrapped objects do not behave well on unicode call

2011-02-16 Thread Christian Zagrodnick
On 2011-02-16 22:22:53 +0100, Hanno Schlichting said: On Wed, Feb 16, 2011 at 10:19 PM, Christian Zagrodnick c...@gocept.com wrote: 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