René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"typing docs: Use soft deprecation","articleBody":"A while ago we introduced the concept of \"soft deprecation\" in PEP 387 (https://peps.python.org/pep-0387/#soft-deprecation): for things that we no longer recommend using, but which we aren't planning to remove in the near future.\n\nThe typing docs already list four classes of objects that are deprecated without a scheduled removal (https://docs.python.org/3.14/library/typing.html#deprecation-timeline-of-major-features):\n\n* Pre-PEP-585 generic aliases (e.g. `List`)\n* `Text`\n* `Hashable` and `Sized`\n* `TypeAlias`\n\nI'd like to also soft-deprecate the following:\n\n* `Optional` (obviated by PEP-604)\n* `NoReturn` (prefer `Never`)\n* `typing.ForwardRef` (deprecated alias for `annotationlib.ForwardRef`)\n* `types.UnionType` (deprecated alias for `typing.Union`)\n* Creating a `Union` using subscripting (`Union[A, B]` instead of `A | B`) (PEP-604)\n* Creating a `TypeVar`, `ParamSpec`, or `TypeVarTuple` using the constructor directly (PEP-695)\n* Directly inheriting from `Generic` (PEP-695)\n\nNone of those will be removable for many years if ever, but I think it's useful to have a clear statement in the docs that the newer syntax is preferred.","author":{"url":"https://github.com/JelleZijlstra","@type":"Person","name":"JelleZijlstra"},"datePublished":"2025-04-25T14:05:56.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":6},"url":"https://github.com/132941/cpython/issues/132941"}