On 12/6/10 10:55 AM, "Martin v. Löwis" wrote:
Of course, with these old systems, I really wonder: why do they need current Python releases? 2.7 will remain available and maintained for some time, and 3.1 will at least see security fixes for some more time - something that the base system itself doesn't receive anymore. So if you needed a Python release for Solaris 8, you could just use Python 2.3, no? We are not going to take the sources of old releases offline.
For things like Solaris 8, I have no thoughts one way or the other-- but considering Windows XP is hitting 10 years next year-- Personally? My entirely theoretical timetable for when I think I'll be able to finally upgrade to Python 3 (where I'll skip to whatever the latest Python 3 is), is actually shorter by at least a few years then my timetable of when I think I'll be able to drop support of Windows XP. Unfortunately.
WinXP is old but *pervasive* still in my experience with small businesses / customers. Many aren't even considering making a plan for Win7 yet.
So if two years rolls around and Python 3.x (where 'x' is 'whatever is current') isn't supported on Windows XP, I'll be very sad, and will have to be stuck on Python 3.x-1 for .. awhile, where "awhile" is out of my control and up to the Masses who are unable or can't be bothered with fixing what works for them w/ WinXP.