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 ezio.melotti
Recipients BreamoreBoy, docs@python, ezio.melotti, georg.brandl, giampaolo.rodola, josiahcarlson, lehmannro, python-dev
Date 2014-06-20.22:57:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1403305023.11.0.600441494951.issue6916@psf.upfronthosting.co.za>
In-reply-to
Content
I don't think removing the documentation for a deprecated item is a good solution.  If people find it somewhere (old code, googling, via dir()) and find no related documentation, they might keep using it.
If it's clearly documented that the item exists but it's deprecated, people will avoid it (or at least be aware of what it does and the reason why it's deprecated).

I think it would be better to add back the documentation with a deprecated-removed directive, and possibly add warnings in the code (if they are not there already).  In future versions we can remove code and docs together.
History
Date User Action Args
2014-06-20 22:57:03ezio.melottisetrecipients: + ezio.melotti, georg.brandl, josiahcarlson, giampaolo.rodola, lehmannro, docs@python, BreamoreBoy, python-dev
2014-06-20 22:57:03ezio.melottisetmessageid: <1403305023.11.0.600441494951.issue6916@psf.upfronthosting.co.za>
2014-06-20 22:57:03ezio.melottilinkissue6916 messages
2014-06-20 22:57:02ezio.melotticreate