R. David Murray wrote:
On Tue, 15 Sep 2009 at 19:02, Laura Creighton wrote:
And there may be things that are so badly written that we actually want
to throw them out of the standard library before people start using
them.
A note 'this module only exists for backwards compatibility, we
recommend that you use XXX instead' will not be good enough for the
purpose, we really want to stamp out the use of this mistake as soon
and as well as possible. This could happen.
On a smaller scale, it did a while ago. Consider ConfigParser and
SafeConfigParser. Although in that case the docs about the
deprecation are not even as good as they could be (see
http://bugs.python.org/issue6517).
Two examples of deprecated modules in the Python documentation:
http://docs.python.org/library/md5.html
http://docs.python.org/library/mimewriter.html
The deprecation notice could be stronger / more prominent.
Michael
--David
_______________________________________________
stdlib-sig mailing list
stdlib-sig@python.org
http://mail.python.org/mailman/listinfo/stdlib-sig
--
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog
_______________________________________________
stdlib-sig mailing list
stdlib-sig@python.org
http://mail.python.org/mailman/listinfo/stdlib-sig
