[Linaro-dev] Python2.5 compatibilty requirement for the Infrastructure Team

[James Westby]

On Tue, 29 Jun 2010 13:43:40 +0200, Zygmunt Bazyli Krynicki <zygmunt.krynicki at linaro.org> wrote:
> Hello everyone.
> 
> Our current developer guidelines for python development state that we
> should support both python2.5 and python2.6.
> 
> I'd like to ask if python2.5 can be dropped from the list. I just took
> the steps required to test python2.5 (and removed 2.6-only features in
> the process). I had to use Hardy VM to do so because python 2.5 is no
> longer available in the Lucid archive. Doing additional testing in a VM
> is cumbersome and error-prone as we can accidentally slip in a 2.6-only
> code or trigger 2.5 bug we didn't know about and it might go untested.
> 
> Can we rationalise the requirements for supporting python2.5 and if so,
> devise a sensible testing plan for our python development?

Something like buildbot/hudson would be more appropriate than each
developer having a 2.5 VM.

The aim of supporting 2.5 is to allow it to be used on machines that
aren't running the latest release. We won't control the deployment
environment in all cases.

I would actually lean towards supporting 2.4 too, but there is
diminshing returns.

Thanks,

James