[issue10669] Document Deprecation Warnings and how to fix

Cheryl Sabella added the comment: If this is change is still desirable, I think it might be a good issue for someone who had contributed a few patches and is looking for something a little more challenging to work on. -- nosy: +cheryl.sabella, mdk, willingc stage: -> needs patch ver

[issue10669] Document Deprecation Warnings and how to fix

Changes by Ezio Melotti : -- nosy: +chris.jerdonek versions: +Python 3.3, Python 3.4 ___ Python tracker ___ ___ Python-bugs-list maili

[issue10669] Document Deprecation Warnings and how to fix

Changes by Éric Araujo : -- components: -2to3 (2.x to 3.0 conversion tool) ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue10669] Document Deprecation Warnings and how to fix

Éric Araujo added the comment: PEP 4 and PEP 290 are related to this subject, but not comprehensive, not on docs.python.org, and not tutorial-like. I think we could try Ezio’s idea. Sphinx can produce a document containing only version* directives (“make changes”). If such a document is cle

[issue10669] Document Deprecation Warnings and how to fix

Raymond Hettinger added the comment: FWIW, whatsnew is not primary documentation -- it should not be the sole or central source of anything except a highlevel overview and examples for the author's choice of selected version differences to highlight. A howto document would work best as a cen

[issue10669] Document Deprecation Warnings and how to fix

Ezio Melotti added the comment: 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 inhe

[issue10669] Document Deprecation Warnings and how to fix

Terry J. Reedy added the comment: The issue is not the specific warnings Rusi got but how, in general, one can get more information when the warnings are too cryptic to deal with. One response might be that DeprecationWarnings should be much wordier than they are -- a paragraph of a few sente