[Python-Dev] API deprecations in Python 3, from a Python 2 perspective
Eric Smith
eric at trueblade.com
Thu Mar 17 20:22:36 CET 2011
More information about the Python-Dev mailing list
Thu Mar 17 20:22:36 CET 2011
- Previous message: [Python-Dev] API deprecations in Python 3, from a Python 2 perspective
- Next message: [Python-Dev] API deprecations in Python 3, from a Python 2 perspective
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 03/17/2011 03:08 PM, Jesus Cea wrote: > I would suggest to keep deprecating things in 3.x, BUT keeping the > deprecated stuff around (maybe reimplementing them using the new stuff) > until we decide is safe to axe it, instead of the regular 3.x > deprecates, 3.(x+1) cleans up. At some point, didn't we say PendingDeprecationWarning in version x, DeprecationWarning in x+1, and removal in x+2? That's what I've been doing, but it's not what PEP 5 says. Removing in x+2 would lengthen the timeframe, although I agree with Guido that we should be extra careful for the next several years because of people moving directory from 2.7 to (say) 3.5. Eric.
- Previous message: [Python-Dev] API deprecations in Python 3, from a Python 2 perspective
- Next message: [Python-Dev] API deprecations in Python 3, from a Python 2 perspective
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list