This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gregory.p.smith
Recipients benjamin.peterson, giampaolo.rodola, gpolo, gregory.p.smith, gvanrossum, michael.foord, pitrou, pupeno, purcell, rhettinger, skip.montanaro
Date 2009-03-31.20:01:26
SpamBayes Score 5.140525e-05
Marked as misclassified No
Message-id <1238529688.76.0.483517550216.issue2578@psf.upfronthosting.co.za>
In-reply-to
Content
trunk r70878 has the code issue an actual PendingDeprecationWarning for
the fail* methods and documents them as deprecated.  If anyone has a
better idea of a better way to state those deprecations in the docs,
feel free to jump in here.

I was unaware of the PendingDeprecationWarning (ignored by default)
prior to this.  I think that is what Guido was suggesting.  The question
of if we can do an actual DeprecationWarning for 3.1 or not still stands.
History
Date User Action Args
2009-03-31 20:01:28gregory.p.smithsetrecipients: + gregory.p.smith, gvanrossum, skip.montanaro, rhettinger, purcell, pitrou, giampaolo.rodola, pupeno, benjamin.peterson, gpolo, michael.foord
2009-03-31 20:01:28gregory.p.smithsetmessageid: <1238529688.76.0.483517550216.issue2578@psf.upfronthosting.co.za>
2009-03-31 20:01:27gregory.p.smithlinkissue2578 messages
2009-03-31 20:01:27gregory.p.smithcreate