PEP 387: clarify that the SC should be consulted when a warning cannot be provided
This commit is contained in:
parent
c8ad36c2d7
commit
671b6a84aa
|
@ -101,6 +101,9 @@ Basic policy for backwards compatibility
|
|||
* Similarly a feature cannot be removed without notice between any two
|
||||
consecutive releases.
|
||||
|
||||
* For changes that are unable to raise a deprecation warning, consult
|
||||
with the steering council.
|
||||
|
||||
* The steering council may grant exceptions to this policy. In
|
||||
particular, they may shorten the required deprecation period for a
|
||||
feature. Exceptions are only granted for extreme situations such as
|
||||
|
@ -145,6 +148,9 @@ several releases:
|
|||
permanent having reached the declared version. Remove the old
|
||||
version and warning.
|
||||
|
||||
6. If a warning cannot be provided to users, consult with the steering
|
||||
council.
|
||||
|
||||
|
||||
References
|
||||
==========
|
||||
|
|
Loading…
Reference in New Issue