diff options
| author | Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> | 2022-05-20 22:33:12 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-05-20 22:33:12 (GMT) |
| commit | 24223ec82a6ef7d32e410940567b1d4ba93e0d1d (patch) | |
| tree | 85405bbcc637691847949d041b0c866d36319432 /Lib/test/_testcppext.cpp | |
| parent | 6a3a6ba7a26cac99ce200dd3a5dab9c419676d49 (diff) | |
| download | cpython-24223ec82a6ef7d32e410940567b1d4ba93e0d1d.zip cpython-24223ec82a6ef7d32e410940567b1d4ba93e0d1d.tar.gz cpython-24223ec82a6ef7d32e410940567b1d4ba93e0d1d.tar.bz2 | |
gh-92611: Clarify planned removal version in PEP 594-deprecated modules (GH-92793) (GH-93026)
As discussed in GH-92611 and GH-92564 and as a followup to PR GH-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 GH-92792 ; if we decide to backport that PR, the upgrade to using `deprecated-removed` on those functions can be moved to this one.
(cherry picked from commit 31fa41ed689528505c0e0cf25777773b7e81c834)
Co-authored-by: CAM Gerlach <CAM.Gerlach@Gerlach.CAM>
Diffstat (limited to 'Lib/test/_testcppext.cpp')
0 files changed, 0 insertions, 0 deletions