gh-92308: Add a future pending removal #31
Conversation
| ================================== | ||
|
|
||
| The following APIs were deprecated in earlier Python versions and will be removed, | ||
| although there is currently no date scheduled for their removal. |
There was a problem hiding this comment.
I'm not sure that it's a good idea of repeating this in each What's New in Python 3.x document. What if it's kept as "pending deprecated" for 10 versions? Should we copy/paste this text in 10 documents?
There was a problem hiding this comment.
Yes, the idea is to increase visibility of things to be removed.
We still want users to change their code for this, even if it's going to be around for a while.
A problem with deprecations is users don't know about them until removal, and sometimes long deprecation periods are to give folk more time to update. All the more reason to list them.
When we have a dedicated deprecations page, we could skip listing things here and instead link to the dedicated page. There's quite a few open-ended deprecations around, so it would also be useful for maintainers to review if they can be removed yet.
There was a problem hiding this comment.
When we have a dedicated deprecations page, we could skip listing things here and instead link to the dedicated page.
If we want to automate the creation of the list/table, a dedicated page would be easier to handle, and won't have to necessarily conform to the structure of the whatsnew.
There's quite a few open-ended deprecations around
See python#92564
|
Can I close this? :) |
|
Yes, let's continue in python#92562! |
Add the first deprecation from https://docs.python.org/3.10/whatsnew/3.10.html#deprecated as a pending removal for https://docs.python.org/3.11/whatsnew/3.11.html#deprecated, and edit a bit.
This one can't be boiled down to a single function/method/constant name, so the original description is kept, with a bit of light editing.
No version has been set for this deprecation, so it goes in a "future" section.