zope.testing 4.0.0 coming up.
I've been working on zope.tetsing lately. The main impetus behind this is Python 3 compatibility, but also general cleanup. This work was discussed on #zope bu Jim Fulton, Stephan Richter, Charlie Clark and me. The conclusion was to release a backwards incompatible zope.testing 4.0.0. The backwards incompatibility is the following: 1. zope.testing.testrunner is now in it's own module, zope.testrunner. I will add a deprecation warning to trunk first, and we'll have to release a new zope.testing 3.x version, then 4.0.0 can be merged. 2. zope.testing.doctest will be dropped. There is already a deprecation warning about this. zope.testing 4.0.0 will support Python 3. Questions? :) -- Lennart Regebro: http://regebro.wordpress.com/ Python 3 Porting: http://python-incompatibility.googlecode.com/ +33 661 58 14 64
On Tue, Apr 27, 2010 at 8:30 PM, Lennart Regebro <regebro@gmail.com> wrote:
I've been working on zope.tetsing lately. The main impetus behind this is Python 3 compatibility, but also general cleanup. This work was discussed on #zope bu Jim Fulton, Stephan Richter, Charlie Clark and me. The conclusion was to release a backwards incompatible zope.testing 4.0.0.
...
Questions? :)
Is it too late for me to introduce another mildly backwards incompatible change? I'd like to add a method to OutputFormatter to handle the specific case of layer setup/teardown failing and change the rest of the runner to call that instead of error. jml
On Tue, Apr 27, 2010 at 21:49, Jonathan Lange <jml@mumak.net> wrote:
On Tue, Apr 27, 2010 at 8:30 PM, Lennart Regebro <regebro@gmail.com> wrote:
I've been working on zope.tetsing lately. The main impetus behind this is Python 3 compatibility, but also general cleanup. This work was discussed on #zope bu Jim Fulton, Stephan Richter, Charlie Clark and me. The conclusion was to release a backwards incompatible zope.testing 4.0.0.
...
Questions? :)
Is it too late for me to introduce another mildly backwards incompatible change?
I'd like to add a method to OutputFormatter to handle the specific case of layer setup/teardown failing and change the rest of the runner to call that instead of error.
I have no opinion on this. How many tests break in Plone when you do this change? :) -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64
On Tue, Apr 27, 2010 at 3:30 PM, Lennart Regebro <regebro@gmail.com> wrote:
I've been working on zope.tetsing lately. The main impetus behind this is Python 3 compatibility, but also general cleanup. This work was discussed on #zope bu Jim Fulton, Stephan Richter, Charlie Clark and me. The conclusion was to release a backwards incompatible zope.testing 4.0.0.
The backwards incompatibility is the following:
1. zope.testing.testrunner is now in it's own module, zope.testrunner. I will add a deprecation warning to trunk first, and we'll have to release a new zope.testing 3.x version, then 4.0.0 can be merged. 2. zope.testing.doctest will be dropped. There is already a deprecation warning about this.
zope.testing 4.0.0 will support Python 3.
Questions? :)
Just a comment that we should be prepared to maintain zope.testing 3 for some period of time. Maybe we should explicitly limit this period (e.g. through the end of 2010.) Jim -- Jim Fulton
participants (3)
-
Jim Fulton -
Jonathan Lange -
Lennart Regebro