[Python-Dev] Process to remove a Python feature (original) (raw)
Serhiy Storchaka storchaka at gmail.com
Tue May 8 12:40:03 EDT 2018
- Previous message (by thread): [Python-Dev] Process to remove a Python feature
- Next message (by thread): [Python-Dev] Process to remove a Python feature
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
04.05.18 22:08, Matthias Bussonnier пише:
Maybe to push people forward, but from experience it is hard to predict future, so saying when it will be remove is hard.
Right. But the data of removing is usually specified when the code for removing already is written, or even merged in the next branch. This is true for most warnings introduced in 3.7 that warns about the removal in 3.8. This is true for Py3k warnings backported to 2.7.
In short-term deprecations you have the only one release in which the warning is emitted.
- Previous message (by thread): [Python-Dev] Process to remove a Python feature
- Next message (by thread): [Python-Dev] Process to remove a Python feature
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]