[Numpy-discussion] Travis-CI stopped supporting Python 3.1, but added 3.3

Nathaniel Smith njs@pobox....
Fri Dec 21 14:05:14 CST 2012


On Fri, Dec 21, 2012 at 1:23 AM, Ondřej Čertík <ondrej.certik@gmail.com> wrote:
> Hi,
>
> I noticed that the 3.1 tests are now failing. After clarification with
> the Travis guys:
>
> https://groups.google.com/d/topic/travis-ci/02iRu6kmwY8/discussion
>
> I've submitted a fix to our .travis.yml (and backported to 1.7):
>
> https://github.com/numpy/numpy/pull/2850
> https://github.com/numpy/numpy/pull/2851
>
> In case you were wondering. Do we need to support Python 3.1?
> We could in principle test 3.1 just like we test 2.4. I don't know if
> it is worth the pain.

It probably isn't much pain, since Python is easy to compile, and I
don't think we've been running into many cases where supporting 3.1
required workarounds yet? (As compared to 2.4, where we get
compatibility-breaking patches constantly.)

It's a crude metric and I'm not sure what conclusion it suggests, but
we have download stats for the different python-version-specific
pre-built numpy binaries:
  http://sourceforge.net/projects/numpy/files/NumPy/1.6.1/
  http://pypi.python.org/pypi/numpy/1.6.1
  http://sourceforge.net/projects/numpy/files/NumPy/1.6.2/
  http://pypi.python.org/pypi/numpy/1.6.2

It looks like python 2.5 is several times more popular than 3.1, and
its popularity is dropping quickly. (30% fewer downloads so far for
1.6.2 than 1.6.1, even though 1.6.2 has more downloads overall.)

-n


More information about the NumPy-Discussion mailing list