-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Jan 27, 2009, at 3:48 PM, Martin v. Löwis wrote:
Releasing 3.1 6 months after 3.0 sounds reasonable; I don't think
it should be released earlier (else 3.0 looks fairly ridiculous).
It sounds like my approval of Raymond's removal of certain
(admittedly
obsolete) operators from the 3.0 branch was premature. Barry at least
thinks those should be rolled back. Others?
I agree that not too much harm is done by removing stuff in 3.0.1 that
erroneously had been left in the 3.0 release - in particular if 3.0.1
gets released quickly (e.g. within two months of the original
release).
If that is an acceptable policy, then those changes would fall under
the policy. If the policy is *not* acceptable, a lot of changes to
3.0.1 need to be rolled back (e.g. the ongoing removal of __cmp__
fragments)
I have no problem with removing things that were advertised and/or
documented to be removed in 3.0 but accidentally were not. That seems
like a reasonable policy to me. However, if we did not tell people
that something was going to be removed, then I don't think we can
really remove it in 3.0.
Barry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSX+S4nEjvBPtnXfVAQIjuQQAucsAp79ZtlcOq1GPiwDaEoYMKTEgkkNp
hLgdDW85ktmFf0xHl/KAU8lcxeaiWGepefsRxsx7c5fX6UIVZPUHDvkDkf5rImx6
wg7Nin2MirLT/lXY7a8//N+5TwLqIBTLLEfAIAFvDhrQT/CuMfZej7leB7BAd7Ti
puLWYYYUL+M=
=pK8E
-----END PGP SIGNATURE-----
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
