[TIP] unittest2 supported versions
robertc at robertcollins.net
Tue Oct 21 12:26:03 PDT 2014
Ok, I'm going to go ahead (provisionally) and make 2.6 the minimum
version. If someone steps up to maintain 2.5 and below, we can do that
the way 2.3 was done - as a separate tree. Perhaps published as
binaries into pypi under unittest2 for convenience.
With 2.6 as the minimum version, single source is now possible for
unittest2 and unittest2py3k, so we can drop that extra package (e.g.
replace it with an empty package depending on unittest2.
On 21 October 2014 19:26, Kushal Das <kushaldas at gmail.com> wrote:
> On Tue, Oct 21, 2014 at 7:17 AM, Robert Collins
> <robertc at robertcollins.net> wrote:
>> unittest2 serves as a backport of unittest features to older python.
>> What versions does it need to support?
>> It currently supports 2.4+, but even 2.6 is now fully dead.
>> So I'd like to suggest that the versions which Python itself is doing
>> security fixes on be the only versions that we test against - I don't
>> want to have to run non-security-supported releases of Python in order
>> to test that new releases of unittest2 work.
> 2.6 is very much alive due to RHEL/CentOS6.x releases. Most of the
> are running those.
> CPython Core Developer
Robert Collins <rbtcollins at hp.com>
HP Converged Cloud
More information about the testing-in-python