<p dir="ltr">2.6+ is both what's convenient for me (bias) and what I tend to support when writing my own software. I use unittest2 to do so.</p>
<p dir="ltr">The extra syntax and functionality in 2.7 tends to be easy to avoid.</p>
<p dir="ltr">-J</p>
<div class="gmail_quote">On 20 Oct 2014 21:48, "Robert Collins" <<a href="mailto:robertc@robertcollins.net">robertc@robertcollins.net</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">unittest2 serves as a backport of unittest features to older python.<br>
<br>
What versions does it need to support?<br>
<br>
It currently supports 2.4+, but even 2.6 is now fully dead.<br>
<br>
So I'd like to suggest that the versions which Python itself is doing<br>
security fixes on be the only versions that we test against - I don't<br>
want to have to run non-security-supported releases of Python in order<br>
to test that new releases of unittest2 work.<br>
<br>
-Rob<br>
<br>
--<br>
Robert Collins <<a href="mailto:rbtcollins@hp.com">rbtcollins@hp.com</a>><br>
Distinguished Technologist<br>
HP Converged Cloud<br>
<br>
_______________________________________________<br>
testing-in-python mailing list<br>
<a href="mailto:testing-in-python@lists.idyll.org">testing-in-python@lists.idyll.org</a><br>
<a href="http://lists.idyll.org/listinfo/testing-in-python" target="_blank">http://lists.idyll.org/listinfo/testing-in-python</a><br>
</blockquote></div>