[Python-Dev] Process to remove a Python feature (original) (raw)

Brett Cannon brett at python.org
Thu May 3 15:55:26 EDT 2018

On Thu, 3 May 2018 at 12:01 Facundo Batista <facundobatista at gmail.com> wrote:

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?

I don't know if we need a history section as the What's New docs cover that. But having a PEP or some other file/doc that acts like a future What's New but for removals seems like a reasonable idea.

-Brett

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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20180503/0fae1a0e/attachment.html>

More information about the Python-Dev mailing list