| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Co-authored-by: Mariatta <Mariatta@users.noreply.github.com>
|
Should we add this to the pending-removal-in-future.rst? |
Sorry, something went wrong.
|
@Mariatta, could you please look again at this PR? |
Sorry, something went wrong.
|
Please see #125871 as a small docs update. |
Sorry, something went wrong.
It's deprecated in Python 3.14: python/cpython#124664
It's deprecated in Python 3.14: python/cpython#124664
|
I'm a little late to the party, but I don't understand why PendingDeprecationWarning was used here. The docs, and warning message contradict the exception saying it is deprecated? Can it be updated to DeprecationWarning if it is deprecated, otherwise I think we should remove the .. deprecated:: and rephrase the warning messages. |
Sorry, something went wrong.
|
We use the deprecated directive even if there is no warning at runtime (they can be added latter). This differs from soft-deprecated where we do not plan runtime warning or deletion. |
Sorry, something went wrong.
|
Yes, but I still don't understand why we're using PendingDeprecationWarning instead of DeprecationWarning here if it is deprecated? |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
📚 Documentation preview 📚: https://cpython-previews--124664.org.readthedocs.build/