[Python-Dev] Process to remove a Python feature (original) (raw)
Facundo Batista facundobatista at gmail.com
Thu May 3 15:01:11 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 ]
2018-05-02 14:24 GMT-03:00 Brett Cannon <brett at python.org>:
Maybe we should create a tool to list features scheduled for removal, and open a discussion to check each removal? I don't know if a tool is necessary. We could have a meta issue or text file somewhere to track what's to be removed in a certain version.
Maybe a specific PEP that list all removals that happened, those that will happen next version, and next ones after that?
IOW, a single point where one can see which features/details will fly away and when.
Probably it's a good idea to see everything at once and evaluate if "we're removing too many things at once", and have a better deprecation/removal cadence.
-- . Facundo
Blog: http://www.taniquetil.com.ar/plog/ PyAr: http://www.python.org/ar/ Twitter: @facundobatista
- 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 ]