[Python-Dev] Should we drop active support of OSF/1?

Jesus Cea jcea at jcea.es
Mon May 3 23:39:45 CEST 2010


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/05/10 21:55, "Martin v. Löwis" wrote:
> Just to rephrase: the point of this deprecation cycle is to give users a
> chance to take over maintenance, and to declare, in public, that they
> are interested in that port. If nobody steps forward, we can safely
> assume that nobody cares.

http://bugs.python.org/issue8606 . I will take care of the final cleanup
in 3.3, if nobody stands up to keep OSF* alive.

I am deprecating OSF*. If it is "too much", we can change it to "OSF1".

- -- 
Jesus Cea Avion                         _/_/      _/_/_/        _/_/_/
jcea at jcea.es - http://www.jcea.es/     _/_/    _/_/  _/_/    _/_/  _/_/
jabber / xmpp:jcea at jabber.org         _/_/    _/_/          _/_/_/_/_/
.                              _/_/  _/_/    _/_/          _/_/  _/_/
"Things are not so easy"      _/_/  _/_/    _/_/  _/_/    _/_/  _/_/
"My name is Dump, Core Dump"   _/_/_/        _/_/_/      _/_/  _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQCVAwUBS99CoJlgi5GaxT1NAQLSygQAiYD0UQAKl2vv1alwmMSP02AgHxN9e3Le
bfMqysr2BE9fnG3WQlUKFn6pjbnnANFU2HRhTUJkaCNslewnUeg6pQ/s0xu321GL
HQ6v6JHSOXxRoyyZ21Wq2ECNg+tYWGkM7Eohsif8XMjTeL0lP7ddYZSFaJbK0PfM
BSK6DAV93/o=
=nlYU
-----END PGP SIGNATURE-----


More information about the Python-Dev mailing list