Re: [Zope-dev] Puzzle re zope.pytest
Hi Uli, Thanks for your reply to clarify the history of zope.pytest. On 05/17/2012 07:22 AM, Uli Fouquet wrote: > > On Wed, 16 May 2012 03:40:17 -0500 Jeff Rush wrote: > >> 5) the unit tests for zope.pytest itself are failing with: >>> from zope.interface.interfaces import ComponentLookupError >> E ImportError: cannot import name ComponentLookupError > > You need at least zope.interface 3.8.0. Looks like you're using an older > version. Yes, for backward compatibility with existing packages, we are using Zope 2.12.x which has an older zope.interface in its ZTK. > I admit, though, that I am not too deep into py.test. If you're an > experienced py.test user, we might could work out something together and > make it more usable. I'd be happy to learn more about py.test from > someone more experienced. No, I'm new to py.test. We had heard good things about it and, a post here on-list (from Jim Fulton) that zope.testrunner should be replaced with a more modern testrunner. I'm not the right one to enhance zope.pytest to better integrate with py.test though. > If, however, you're after a quick, ready-to-use, comprehensive framework > for testing Zope applications, you might be better off with other > approaches like the regular Zope testrunner and related libs. Yes, we've been using zope.testrunner here, but some of the developers on the team who are less familiar with Zope don't care for the zope-specific coding in our tests. They had hoped to move us forward with a more general test framework but I guess it can't happen right now. I'm wondering if there is a way to run the improved test APIs of py.test while running it under the zope.testrunner. That way we'd get some of the benefit of py.test, to move away from the various self.assertEqual() calls and to the cleaner way of py.test. Initial investigation says not, that the API benefits of py.test are closely tied to its testrunner. I thought we could create a py.test-specific testsuite() and use the API internally. -Jeff ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
Re: [Zope-dev] zope-tests - FAILED: 5, OK: 38
On 05/19/2012 09:00 PM, Zope tests summarizer wrote: > [1]FAILED ZTK 1.0dev / Python2.4.6 Linux 64bit > https://mail.zope.org/pipermail/zope-tests/2012-May/063250.html > > > [2]FAILED ZTK 1.0dev / Python2.5.5 Linux 64bit > https://mail.zope.org/pipermail/zope-tests/2012-May/063252.html > > > [3]FAILED ZTK 1.0dev / Python2.6.7 Linux 64bit > https://mail.zope.org/pipermail/zope-tests/2012-May/063251.html These three are all buildout failures due to mr.developer: > Can't switch package 'zope.preference' to > 'svn://svn.zope.org/repos/main/zope.preference/branches/3.8' because > it's dirty. I'm not sure why only that one is horked: I changed it the same way I changed all the others. At a guess, we need to forcibly remove the zope.preference directory and > [4]FAILED winbot / zope.app.appsetup_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-May/063249.html This one is still due to zope.index 4.0.0 deprecations in doctest-asserted subprocess output. I need to think about how to fix that (releasing a silent 4.0.1 is the current plan). > [5]FAILED winbot / zope.configuration_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-May/063248.html More Windows-only whack-a-mole needed. :( Tres. -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design"http://palladion.com ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
Re: [Zope-dev] zope.interface 4.0.0 considered annoying.
On Sun, May 20, 2012 at 12:08 AM, Tres Seaver wrote: > On 05/19/2012 07:23 PM, Jim Fulton wrote: ... >> I'd forgotten the fail silently bit. Can't we make the fail loudly >> for Python 3? > > They already do: 4.0.0 makes them exceptions under Python3: that fact > was actually my rationale for the warnings under Python2, to allow folks > to find and remediate them before porting. That's reasonable. I'd probably have had the same inclination -- until I experienced the result. :) > I will release a 4.0.1 silencing the warnings unless somebody speaks up > in their favor. Thanks. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://www.dublinstore.com/ ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
Re: [Zope-dev] zope.interface 4.0.0 considered annoying.
On 05/19/2012 07:23 PM, Jim Fulton wrote: > On Sat, May 19, 2012 at 5:59 PM, Tres Seaver > wrote: >> On 05/19/2012 12:12 PM, Jim Fulton wrote: >>> The declaration-syntax warnings in the zope.interface 4.0.0 are >>> annoying and mostly pointless. >>> >>> There will be enough pain in porting applications to Python 3, >>> avoiding the surprise of having to use a different >>> interface-declaration syntax will not be of any consequence. >>> >>> While the deprecation warning may provide some tiny benefit, the >>> annoyance, especially for applications or libraries that still >>> support Python 2.5 far outweights the benefit. >> >> We're in an odd spot: the Python3 support for zope.interface >> mostly works, but the class advice bits (implements, >> implementsOnly, classProvides) fail silently under Python3 before >> 4.0.0: they literally have no effect due to changes in class >> initialization machinery. zope.interface 4.0.0 changes those silent >> failures into exceptions (which is what I thought you were going to >> complain about). > > I'd forgotten the fail silently bit. Can't we make the fail loudly > for Python 3? They already do: 4.0.0 makes them exceptions under Python3: that fact was actually my rationale for the warnings under Python2, to allow folks to find and remediate them before porting. I will release a 4.0.1 silencing the warnings unless somebody speaks up in their favor. Tres. -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design"http://palladion.com ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
[Zope-dev] zope-tests - FAILED: 5, OK: 38
This is the summary for test reports received on the zope-tests list between 2012-05-18 00:00:00 UTC and 2012-05-19 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received Bluebream / Python2.5.5 64bit linux Bluebream / Python2.6.7 64bit linux Bluebream / Python2.7.2 64bit linux ZTK 1.0 / Python2.4.6 Linux 64bit ZTK 1.0 / Python2.5.5 Linux 64bit ZTK 1.0 / Python2.6.7 Linux 64bit [1]ZTK 1.0dev / Python2.4.6 Linux 64bit [2]ZTK 1.0dev / Python2.5.5 Linux 64bit [3]ZTK 1.0dev / Python2.6.7 Linux 64bit ZTK 1.1 / Python2.5.5 Linux 64bit ZTK 1.1 / Python2.6.7 Linux 64bit ZTK 1.1 / Python2.7.2 Linux 64bit ZTK 1.1dev / Python2.5.5 Linux 64bit ZTK 1.1dev / Python2.6.7 Linux 64bit ZTK 1.1dev / Python2.7.2 Linux 64bit Zope 3.4 KGS / Python2.4.6 64bit linux Zope 3.4 KGS / Python2.5.5 64bit linux Zope 3.4 Known Good Set / py2.4-32bit-linux Zope 3.4 Known Good Set / py2.4-64bit-linux Zope 3.4 Known Good Set / py2.5-32bit-linux Zope 3.4 Known Good Set / py2.5-64bit-linux Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.6 : Linux Zope-2.12-alltests Python-2.6.6 : Linux Zope-2.13 Python-2.6.6 : Linux Zope-2.13-alltests Python-2.6.6 : Linux Zope-trunk Python-2.6.6 : Linux Zope-trunk-alltests Python-2.6.6 : Linux winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [4]winbot / zope.app.appsetup_py_265_32 [5]winbot / zope.configuration_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -- [1]FAILED ZTK 1.0dev / Python2.4.6 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2012-May/063250.html [2]FAILED ZTK 1.0dev / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2012-May/063252.html [3]FAILED ZTK 1.0dev / Python2.6.7 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2012-May/063251.html [4]FAILED winbot / zope.app.appsetup_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-May/063249.html [5]FAILED winbot / zope.configuration_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-May/063248.html ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
Re: [Zope-dev] zope.interface 4.0.0 considered annoying.
On Sat, May 19, 2012 at 5:59 PM, Tres Seaver wrote: > On 05/19/2012 12:12 PM, Jim Fulton wrote: >> The declaration-syntax warnings in the zope.interface 4.0.0 are >> annoying and mostly pointless. >> >> There will be enough pain in porting applications to Python 3, >> avoiding the surprise of having to use a different >> interface-declaration syntax will not be of any consequence. >> >> While the deprecation warning may provide some tiny benefit, the >> annoyance, especially for applications or libraries that still support >> Python 2.5 far outweights the benefit. > > We're in an odd spot: the Python3 support for zope.interface mostly > works, but the class advice bits (implements, implementsOnly, > classProvides) fail silently under Python3 before 4.0.0: they literally > have no effect due to changes in class initialization machinery. > zope.interface 4.0.0 changes those silent failures into exceptions (which > is what I thought you were going to complain about). I'd forgotten the fail silently bit. Can't we make the fail loudly for Python 3? Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://www.dublinstore.com/ ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
Re: [Zope-dev] zope.interface 4.0.0 considered annoying.
On 05/19/2012 12:12 PM, Jim Fulton wrote: > The declaration-syntax warnings in the zope.interface 4.0.0 are > annoying and mostly pointless. > > There will be enough pain in porting applications to Python 3, > avoiding the surprise of having to use a different > interface-declaration syntax will not be of any consequence. > > While the deprecation warning may provide some tiny benefit, the > annoyance, especially for applications or libraries that still support > Python 2.5 far outweights the benefit. We're in an odd spot: the Python3 support for zope.interface mostly works, but the class advice bits (implements, implementsOnly, classProvides) fail silently under Python3 before 4.0.0: they literally have no effect due to changes in class initialization machinery. zope.interface 4.0.0 changes those silent failures into exceptions (which is what I thought you were going to complain about). Note as well that zope.interface 4.0.0 doesn't support Python 2.5 any longer. > I propose that these deprecation warnings be removed. I can do that, if that is the consensus. Tres. -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design"http://palladion.com ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
[Zope-dev] zope.interface 4.0.0 considered annoying.
The declaration-syntax warnings in the zope.interface 4.0.0 are annoying and mostly pointless. There will be enough pain in porting applications to Python 3, avoiding the surprise of having to use a different interface-declaration syntax will not be of any consequence. While the deprecation warning may provide some tiny benefit, the annoyance, especially for applications or libraries that still support Python 2.5 far outweights the benefit. I propose that these deprecation warnings be removed. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://www.dublinstore.com/ ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
