[Twisted-Python] [RFC] Deprecation Policy

[Tristan Seligmann]

* David Ripton <dripton at ripton.net> [2008-04-18 06:13:13 -0700]:

> On 2008.04.18 15:06:10 +1000, Jonathan Lange wrote:
> > CompatibilityPolicy suggests release-based deprecation that is graded
> > over 4 releases: release N PendingDeprecationWarning, N+1
> > DeprecationWarning, N+2 DeprecationError, N+3 remove the
> > functionality.
> > 
> > Ticket #1216 suggests a release-based deprecation policy that is not
> > graded and over 1 release: release N, add DeprecationWarning, release
> > N+1, remove the functionality.
> 
> As a user, I don't see much difference between a
> PendingDeprecationWarning and a DeprecationWarning.  Or between a
> DeprecationError and the code being removed.  Simple is good.

A PendingDeprecationWarning is not visible by default, so users of an
application won't be inundated with DeprecationWarning messages they can
do nothing about; but a developer can turn them on in order to check if
his application is using any deprecated APIs.
-- 
mithrandi, i Ainil en-Balandor, a faer Ambar
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: </pipermail/twisted-python/attachments/20080418/c22c34ca/attachment.sig>