[Python-3000] [Python-Dev] What should the focus for 2.6 be? (original) (raw)
Talin talin at acm.org
Thu Aug 24 05:38:06 CEST 2006
- Previous message: [Python-3000] [Python-Dev] What should the focus for 2.6 be?
- Next message: [Python-3000] Droping find/rfind?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Josiah Carlson wrote:
"Terry Reedy" <tjreedy at udel.edu> wrote:
"Josiah Carlson" <jcarlson at uci.edu> wrote in message news:20060823125951.1A60.JCARLSON at uci.edu...
The intent of my post was to say that all of us want Py3k to succeed, I should hope that we all do.
but I believe that in order for it to succeed that breakage from the 2.x series should be gradual, in a similar way to how 2.x -> 2.x+1 breakage has been gradual. Given that the rate of intentional breakage in the core language (including builtins) has been very minimal, this would take a couple of decades, which to my mind would be a failure. If we could stick with a 12-18 month release schedule, using deprecation and removal in subsequent releases, every removal could happen in 2-3 years. 2.6 could offer every feature of 3.0 (except for backwards-incompatible syntax), warning of removal or relocation (in the case of stdlib reorganization), 3.0 could handle all of the actual syntax changes.
2.6 should also include a powerful 'lint' option that detects use of features not compatible with 3.0. Something like "from future import pedantic" or something along those lines.
-- Talin
- Previous message: [Python-3000] [Python-Dev] What should the focus for 2.6 be?
- Next message: [Python-3000] Droping find/rfind?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]