RetroSearch Browse

Mon Dec 6 19:55:15 CET 2010 · https://mail.python.org/pipermail/python-dev/2010-December/106493.html

Am 06.12.2010 14:40, schrieb Floris Bruynooghe:
> On 6 December 2010 09:18, "Martin v. Löwis" <martin at v.loewis.de> wrote:
>>> Also, it is not clear what to do about distributions/OSs
>>> without any official EOL or life cycles.
>>
>> Here my proposal stands: 10 years, by default.
> 
> How about max(EOL, 10years)?  That sounds like it could be a useful guideline.
> 
> (Personally I'd be sad to see Solaris 8 go in the next few years)

I guess we'll be sorry, then: under that policy, max(EOL, 10years) comes
out as "not supported" (not sure whether you were aware of that).

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.

Regards,
Martin

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2010-December/106493.html below:

[Python-Dev] PEP 11: Dropping support for ten year old systems