PEP 387
Python Enhancement Proposal 387, which formally codifies the concept of soft deprecation. It defines a documentation-level form of deprecation that does not trigger runtime warnings and carries no commitment to remove the deprecated API.
Timeline (last 90 days)
According to PEP 387, soft deprecation means that an API is marked as something that should no longer be used for writing new code, but the official does not commit to or threaten to remove it in the future.
The concept of soft deprecation was first formally standardized by PEP 387 during the Python 3.12 cycle.
All Facts (2)
According to PEP 387, soft deprecation means that an API is marked as something that should no longer be used for writing new code, but the official does not commit to or threaten to remove it in the future.
50%UnverifiedThe concept of soft deprecation was first formally standardized by PEP 387 during the Python 3.12 cycle.
50%