On 2010-02-19 14:10, Guido van Rossum wrote: > Isn't mhlib itself deprecated? (It's gone in Py3k.)
I wouldn't like that, but it is beside my point. If a module is deprecated, then it should not be used in released code. If mhlib is deprecated, it doesn't tell you about it. mhlib uses multifile and multifile does tell you it is deprecated, and that is pretty annoying. > On Fri, Feb 19, 2010 at 4:33 AM, Sjoerd Mullender <sjo...@acm.org> wrote: >> I have noticed that deprecated stuff is still being used in the standard >> Python library. When using modules that contain deprecated stuff you >> get a warning, and as a mere user there isn't much you can do about that. >> >> As a general rule, the Python standard library should not use deprecated >> constructs in non-deprecated (or otherwise deprecated) modules. >> >> The case I am running into is that mhlib uses multifile (in 2.6). > -- Sjoerd Mullender
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
