René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[Docs] add a new Sphinx `VersionChange` directive `.. scheduled-changed::`","articleBody":"# Documentation\n\nFollow the discussion in https://github.com/python/cpython/issues/127405#issuecomment-2532875353:\n\n\u003e No reason to actually use the word \"deprecation\" except to explain what process we're following for changing a user-visible and documented API.\n\nThe change is added in PR #131717:\n\n- #131717\n\n```rst\n   .. versionchanged:: 3.14\n      A deprecation warning will be emitted if the :data:`sys.abiflags` member\n      is accessed on Windows.\n\n      The :data:`sys.abiflags` member will be set to a meaningful value on\n      Windows in Python 3.16. This means the :data:`sys.abiflags` member will\n      always be available on all platforms starting from Python 3.16.\n```\n\nA `.. versionchanged::` directive is not very accurate for this change. It would be nice to have a new directive `.. scheduled-changed::`:\n\n```rst\n   .. scheduled-changed:: 3.14 3.16\n      A deprecation warning will be emitted if the :data:`sys.abiflags` member\n      is accessed on Windows.\n\n      The :data:`sys.abiflags` member will be set to a meaningful value on\n      Windows in Python 3.16. This means the :data:`sys.abiflags` member will\n      always be available on all platforms starting from Python 3.16.\n```\n\nLike the `.. deprecated-removed::` directive:\n\nhttps://github.com/python/cpython/blob/8ada7a9e1435302ec2cb73375122072d0e1cdd6f/Doc/tools/extensions/changes.py#L76-L84","author":{"url":"https://github.com/XuehaiPan","@type":"Person","name":"XuehaiPan"},"datePublished":"2025-03-25T18:37:17.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/131733/cpython/issues/131733"}