As a sample, a few projects have mod_python in their webservers, and expose Python version in the HTTP response headers:
IBERCIVIS: Python 2.5.2 or...@home: Python 2.5.2 PicEvolvr: Python 2.4.3 WUProp: Python 2.5.2 The rest didn't have mod_python (or didn't respond, server down). Note that it's possible to have multiple major Python versions co-existing, so those projects may still have Python 2.6 installed. Even on my own computer I have 2.5.5, 2.6.5, and 3.1.1, with 2.5 used by default in /usr/bin/python. Plus it's possible (though unlikely) that the projects mentioned above are the *only* ones that don't have 2.6 :P -- Nicolas On 6/22/10, Michael Tughan <[email protected]> wrote: > The second question is probably better asked on boinc_projects. Forwarding > to there. > > Do any projects still use Python 2.5 or earlier with BOINC? > > Michael Tughan > > On 2010-06-21, at 11:09 PM, Jeremy Cowles wrote: > >> I may be willing to take this on, but I have two questions: >> >> Do you think it's the right time to support Python 3, that is, does anyone >> else care or want support for it? >> >> and >> >> Will breaking compatibility with Python 2.5 cause problems for any BOINC >> projects? >> >> -- >> Jeremy >> _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
