summaryrefslogtreecommitdiffstats
path: root/Python/pyctype.c
diff options
context:
space:
mode:
authorCAM Gerlach <CAM.Gerlach@Gerlach.CAM>2022-05-20 21:47:51 (GMT)
committerGitHub <noreply@github.com>2022-05-20 21:47:51 (GMT)
commit31fa41ed689528505c0e0cf25777773b7e81c834 (patch)
tree06fc897707612145d6b330bb0a4be06e7f1e5774 /Python/pyctype.c
parent87b9b4e060377f09096db7af977f604749c8a100 (diff)
downloadcpython-31fa41ed689528505c0e0cf25777773b7e81c834.zip
cpython-31fa41ed689528505c0e0cf25777773b7e81c834.tar.gz
cpython-31fa41ed689528505c0e0cf25777773b7e81c834.tar.bz2
gh-92611: Clarify planned removal version in PEP 594-deprecated modules (GH-92793)
As discussed in #92611 and #92564 and as a followup to PR #92612 , this 3.11+ only PR uses the proper `deprecated-removed` role for the modules deprecated by PEP 593 (PEP-594) to clearly indicate to users that a removal version is planned and what it is, so they can prepare accordingly or voice any unanticipated impacts. Related to #92792 ; if we decide to backport that PR, the upgrade to using `deprecated-removed` on those functions can be moved to this one.
Diffstat (limited to 'Python/pyctype.c')
0 files changed, 0 insertions, 0 deletions