<p dir="ltr">It sounded like Holger was referring to dropping support for having python2.6 be the one that you install tox to? Not support for 2.6 toxenvs?</p>
<p dir="ltr">The latter seems (very) premature to me but the former seems reasonable to me at least, I run tox on development machines or CI servers where I could coordinate having 2.7 available, so I'd assume the way to make that decision involves deciding whether CentOS 6 is common enough in CI?)</p>
<div class="gmail_quote">On May 13, 2015 4:09 PM, "Paul Moore" <<a href="mailto:p.f.moore@gmail.com">p.f.moore@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 13 May 2015 at 13:12, Ned Batchelder <<a href="mailto:ned@nedbatchelder.com">ned@nedbatchelder.com</a>> wrote:<br>
> If by "multiple Python minor versions on one OS" you mean my Mac laptop<br>
> running both Python 2.6 and Python 2.7 (and 3.3, 3.4, 3.5, and pypy2,<br>
> pypy3): IME, that is the primary use-case for tox! Maybe we are talking<br>
> about different things?<br>
<br>
That's what I understood as well. I have tox installed in my Python<br>
3.4 environment, and run it from there pretty much exclusively. But I<br>
have Python 2.6, 2.7, 3.3 and 3.4 installed, and have toxenvs for<br>
whichever of those are relevant to my project in tox.ini.<br>
<br>
I know CI environments like Travis run tox multiple times, one for<br>
each Python version (in effect python2.7 -m tox toxenv=py27; python2.6<br>
-m tox toxenv=py26 etc), so losing the ability to run tox under Python<br>
2.6 would hurt those environments. Maybe that's what Robert was<br>
thinking of?<br>
<br>
Paul<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>