| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
I wonder if there was some automation we can add to help ensure that planned deprecations actually happen? Like, maybe a JSON file or some such where the deprecations are recorded (or a script to parse the docs or code). Then, when the new version is created at main, the automation would open some release blockers on those deprecations. What do you think? |
Sorry, something went wrong.
|
@warsaw Probably, grepping docs for .. deprecated-removed:: and headers for Py_DEPRECATED would be better than maintaining another list file. Edit: for \.\. deprecated-removed:: [^ ]+ (\d+).(\d+) and Py_DEPRECATED\((\d+).(\d+)\). |
Sorry, something went wrong.
Yes, using the new warnings._deprecated method will make it clear with RuntimeErrors after the relevant alpha: https://discuss.python.org/t/introducing-warnings-deprecated/14856 |
Sorry, something went wrong.
See also: |
Sorry, something went wrong.
There was a problem hiding this comment.
I left a comment and a couple of minor suggestions -- feel free to disregard them if you think the current version is better.
Sorry, something went wrong.
Co-authored-by: Ezio Melotti <ezio.melotti@gmail.com>
You could also fire a Sphinx warning in the else branch here in the directive (with a check for whether its an alpha, and perhaps an :option: to disable it for special cases), just like warnings._deprecated does. |
Sorry, something went wrong.
Co-authored-by: Ezio Melotti <ezio.melotti@gmail.com>
| :keyword:`for`, :keyword:`if`, :keyword:`in`, :keyword:`is` and :keyword:`or`. | ||
| In a future release it will be changed to a syntax error. (:gh:`87999`) | ||
|
|
||
| * :func:`asyncio.get_event_loop` emits a :exc:`DeprecationWarning` if there is |
There was a problem hiding this comment.
The deprecation plans for this function have changed. See #100970 for the updated deprecation notice.
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks for the note! This PR has got pretty out of date...
Sorry, something went wrong.
|
Will try again in a new PR :) |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Follow on from #92308.
This lists in the What's New page some more deprecations pending removal in: