Doc/c-api/type.rst and Doc/c-api/module.rst mark seven functions .. soft-deprecated:: next. All seven were already in the tree at v3.15.0b1, and Doc/whatsnew/3.15.rst lists exactly those seven under "These following functions are :term:soft deprecated", so next, which expands to the development version, names the wrong release. The 3.15.0b1 commit rewrote 84 :: next tags and none of the soft-deprecated:: ones.
$ git grep -c 'soft-deprecated:: next' v3.15.0b1 -- Doc/c-api/
v3.15.0b1:Doc/c-api/module.rst:3
v3.15.0b1:Doc/c-api/type.rst:4
$ git grep -n 'soft-deprecated:: next' -- Doc/
Doc/c-api/module.rst:856: .. soft-deprecated:: next
Doc/c-api/module.rst:880: .. soft-deprecated:: next
Doc/c-api/module.rst:890: .. soft-deprecated:: next
Doc/c-api/type.rst:831: .. soft-deprecated:: next
Doc/c-api/type.rst:862: .. soft-deprecated:: next
Doc/c-api/type.rst:888: .. soft-deprecated:: next
Doc/c-api/type.rst:913: .. soft-deprecated:: next
Expected: these seven say .. soft-deprecated:: 3.15, like every other soft-deprecated:: directive in the tree.
Activity
gh-157137: Mark the PEP 820 soft deprecations as 3.15, not `next` (#1…
Merge branch 'main' into tachyon-native-callable
pythongh-157137: Mark the PEP 820 soft deprecations as 3.15, not `nex…
pythongh-157137: Mark the PEP 820 soft deprecations as 3.15, not `nex…