(original) (raw)

On Fri, Feb 19, 2010 at 08:40, Sjoerd Mullender <sjoerd@acm.org> wrote:

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.

I see the deprecation warning upon importing mhlib in 2.6 and trunk (with -Wd).