[TIP] Tox problems with Python 2.5, 3.1 and 3.4

Jonathan Eunice jonathan.eunice at gmail.com
Mon Aug 26 08:12:48 PDT 2013

I have seen similar issues. In the case of 2.5 and 3.1, I simply
took them out of the testing lineup.

2.5 is 7 years old (released Sept 2006), beyond the "support window"
of most commercial software. I'd still support it if feasible, but
the current versions of modules I code and test with no longer work
there. This includes even the pip installer.

3.1 is only 4 years old, but it feels similarly behind the mainstream.
3.2 brought in more consistency with the key string/bytes distinction,
and 3.3 finally made some commonsense compatibility-with-Python 2
fixes. py31 feels very "early days, not quite complete" by comparison.

Unless there's a strong need for you to support py25 or py31, might
be easier to declare them versiona non grata than accommodate them.

Re 3.4, I get exactly the same thing. Not sure why. I looked at the 
3.4.0a1 and 3.3.1 code bases (Lib/collections/__init__.py e.g.)
Seems identical.

I think this boils down to "it's an alpha release, and not ready for 
real use."

More information about the testing-in-python mailing list