[Zope-dev] Avoid deprecation warnings in the testrunner

Zvezdan Petkovic zvezdan at zope.com
Thu Dec 24 10:52:25 EST 2009


On Dec 24, 2009, at 10:26 AM, Fabio Tranchitella wrote:

> * 2009-12-24 16:20, Zvezdan Petkovic wrote:
>> Before I release the egg on PyPI:
>> 
>> 	1.  Should we release as 1.1.2 (a minor change), or
>> 	2.  Does the removal of dependency on zope.testing warrants a
>> 	    bump to 1.2.0?
> 
> I think 1.1.2 is okey, you are not changing any behaviour of the package.


zope.minmax-1.1.2 is now on PyPI.


>> FWIW, I preferred zope.testing.doctest reporting of 15 tests because
>> that's the actual number of things being tested in that file, while
>> Python doctest reports 1 test only, because that's a number of test files
>> being run.
> 
> Me too, maybe we should push the changes to doctest upstream to Python?

That will take some serious persuading.

We could argue the above, i.e., that 15 different things were tested in one doctest file.

Unfortunately, when a single test in a doctest file is mixed with prose descriptions to explain parts of the test, zope.testing.doctest counts it as a separate test.

This was considered a misfeature in the past and would probably be rejected for the same reason now.

People are divided in opinion on this and whenever that happens it's hard to push such a change upstream into Python library.

Of course, it may be worth trying if there is a critical mass of supporters.

	Zvezdan



More information about the Zope-Dev mailing list