Re:Viewing Python 3.2 as the successor to Python 2.7
by ubernostrum on Friday October 29, 2010 @04:45PM
(#1848949)
As far as I know, we're doing what the Python dev team expected for large projects: taking some time to deprecate older 2.x releases, working our way toward being 2.6- or 2.7-only, then porting from there.
Nobody who actually paid attention to the Python 3 process expected this to happen quickly, or is under the impression that large projects are taking longer than expected to port.
Nobody who actually paid attention to the Python 3 process expected this to happen quickly, or is under the impression that large projects are taking longer than expected to port.