[Python-Dev] Python 4: don't remove anything, don't break backward compatibility (original) (raw)
Chris Angelico rosuav at gmail.com
Mon Mar 10 18:13:37 CET 2014
- Previous message: [Python-Dev] Python 4: don't remove anything, don't break backward compatibility
- Next message: [Python-Dev] Python 4: don't remove anything, don't break backward compatibility
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Mar 11, 2014 at 4:08 AM, R. David Murray <rdmurray at bitdance.com> wrote:
(That said, I do see some merit to doing some extra cleaning at the 4.0 boundary, just for mental convenience.)
A transition from 3.9 to 4.0 that removes a whole lot of deprecated aliases and such wouldn't be a bad thing. It's technically breaking backward compat (and thus justifying the major version bump), but any code broken by it would have been unidiomatic for the past X versions anyway.
ChrisA
- Previous message: [Python-Dev] Python 4: don't remove anything, don't break backward compatibility
- Next message: [Python-Dev] Python 4: don't remove anything, don't break backward compatibility
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]