Message123780
| Author |
ezio.melotti |
| Recipients |
RusiMody, docs@python, eric.smith, ezio.melotti, rhettinger, terry.reedy |
| Date |
2010年12月11日.06:55:03 |
| SpamBayes Score |
3.8265483e-07 |
| Marked as misclassified |
No |
| Message-id |
<1292050504.73.0.205212664116.issue10669@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
The deprecation notes in the doc should be quite easy to find and can be more verbose, but there are a few cases where the deprecation is not about a specific function but something more "abstract" (e.g. some syntax change, or the "Overriding __eq__ blocks inheritance of __hash__ in 3.x" reported by the OP).
Listing new deprecations in the what's new it's a good idea, but otherwise a clear message (that also suggests how to fix the problem) and a deprecation note in the doc (using the '.. deprecated::' directive) should be enough. |
|