Python 2.3 has been EOL'ed for years. It definitely is not up-to-date, for any reasonable definition of the term. For example, it will have
many unplugged security holes. So will that user's version of OpenSSL
and other libraries. If they don't want to apply security fixes, why
should we even care about their timezones' freshness?

"Want to"?

//Lennart
">

(original) (raw)

On Mon, Oct 1, 2012 at 1:53 PM, Antoine Pitrou <solipsis@pitrou.net> wrote:
Python 2.3 has been EOL'ed for years. It definitely is not up-to-date,
for any reasonable definition of the term. For example, it will have
many unplugged security holes. So will that user's version of OpenSSL
and other libraries. If they don't want to apply security fixes, why
should we even care about their timezones' freshness?

"Want to"?

//Lennart