➜

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 Arfrever, eric.araujo, ezio.melotti, flox, giampaolo.rodola, pitrou, python-dev, rhettinger, terry.reedy, tshepang, vstinner
Date 2012-03-15.01:23:42
SpamBayes Score 0.00042272688
Marked as misclassified No
Message-id <1331774623.78.0.463954388015.issue13248@psf.upfronthosting.co.za>
In-reply-to
Content 
Raymond, I think it's better to leave the documentation and use  "deprecated-removed" to signal clearly that those functions are deprecated and when they will be removed (even if this means 3.4).

IME removing documentation creates more confusion because people that find those functions in some codebase will have an hard time figuring out what they are, where do they come from, if they are deprecated or not and when they will be removed.
History
Date User Action Args
2012-03-15 01:23:43ezio.melottisetrecipients: + ezio.melotti, rhettinger, terry.reedy, pitrou, vstinner, giampaolo.rodola, eric.araujo, Arfrever, flox, tshepang, python-dev
2012-03-15 01:23:43ezio.melottisetmessageid: <1331774623.78.0.463954388015.issue13248@psf.upfronthosting.co.za>
2012-03-15 01:23:43ezio.melottilinkissue13248 messages
2012-03-15 01:23:42ezio.melotticreate