[Python-Dev] What should the focus for 2.6 be? (original) (raw)
Barry Warsaw barry at python.org
Sun Aug 20 17:32:35 CEST 2006
- Previous message: [Python-Dev] What should the focus for 2.6 be?
- Next message: [Python-Dev] What should the focus for 2.6 be?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Aug 20, 2006, at 11:24 AM, Guido van Rossum wrote:
I wonder if it would make sense to focus in 2.6 on making porting of 2.6 code to 3.0 easier, rather than trying to introduce new features in 2.6. We've done releases without new language features before; notable 2.3 didn't add anything new (except making a few future imports redundant) and concentrated on bugfixes, performance, and library additions.
+1, and there are other benefits to this approach too.
First, the pace of change appears to slow, which addresses another
source of complaints. Because instead of a slew of new features
every 18 months, we really see that slew only every three years, with
a stabilizing and bug fixing release in between. Another benefit is
that with a de-emphasis on new features, we can spend more time
improving the library and documentation.
- -Barry
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBROiAk3EjvBPtnXfVAQKeMQP/QBfHJexDveKoj/nfjRjic3+HBvTupkoA bga7GmLV7Rn14AoHf+L6n3IhKkE1sIVXwzUmEoOeVN74h3trJSAeEYPjCF7Vt3// 3fZ4SgAlEy3nsOwRYufUtyYU9r36H7Fn7dKTtj+hJCVAzZdAOERy8ZMAEoSOw+Q4 vNfudLPznDQ= =7D1V -----END PGP SIGNATURE-----
- Previous message: [Python-Dev] What should the focus for 2.6 be?
- Next message: [Python-Dev] What should the focus for 2.6 be?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]