➜

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 larry
Recipients Arfrever, Yury.Selivanov, benjamin.peterson, gvanrossum, larry, neologix, r.david.murray, rosslagerwall, serhiy.storchaka
Date 2012-06-09.04:23:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <[email protected]>
In-reply-to
Content 
> Previously existing redundant functions could be
> deprecated in documentation.

As in, don't start a "deprecation cycle" (warning in 3.3, deprecated in 3.4, gone in 3.5), just document "consider using this other function instead"?  That's probably worth doing.  I wouldn't use the word "deprecated" though, I'd just suggest a "see also".

Maybe we could remove the redundant functions in 4.0.  I'll put it on my wishlist :)
History
Date User Action Args
2012-06-09 04:23:42larrysetrecipients: + larry, gvanrossum, benjamin.peterson, Arfrever, r.david.murray, neologix, Yury.Selivanov, rosslagerwall, serhiy.storchaka
2012-06-09 04:23:42larrysetmessageid: <[email protected]>
2012-06-09 04:23:42larrylinkissue14626 messages
2012-06-09 04:23:41larrycreate