According to bug 724191 [1], our build infrastructure is currently
running the following Python versions:
* Talos - 2.4
* Tests - 2.5.1
* Builds - 2.7.1
* Buildbot - 2.5.1
I find it frustrating that when making improvements to the build and
test systems that I have to target both old and inconsistent versions of
Python. It is so frustrating that it sometimes makes me reconsider
making improvements to these components because I don't want to deal
with the headache!
AFAICT, there is nothing *technical* holding us back from upgrading to
2.6 or 2.7. The Windows mozilla-build environment now ships with 2.7. OS
X 10.7 ships with 2.7.1 (although 2.6 might be the default), and nearly
every *NIX distro ships with 2.6 and/or 2.7. Needless to say, things
seem to just work on 2.6 and 2.7. Instead, the barrier seems to be human
resources and prioritization. With this post, I'm hoping to raise
awareness and get this on the radar.
There is also the question of what to upgrade to. In my ideal world I'd
say move ALL THE THINGS to 2.7 because that is the best 2.x version
available (I think it's safe to say we don't want to deal with 3.x at
this time). But, I can sympathize with people on 2.6 who may suddenly
experience a breakage because someone checked in something requiring 2.7.
So, when can we modernize the build and testing infrastructure and what
should we consolidate to?
[1]
https://bugzilla.mozilla.org/show_bug.cgi?id=724191
Gregory Szorc
g...@mozilla.com