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.

classification
Title: mhlib does not emit deprecation warning
Type: behavior Stage: resolved
Components: Library (Lib) Versions: Python 2.7
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: eric.araujo, l0nwlf, r.david.murray, sjoerd
Priority: low Keywords:

Created on 2010-02-19 14:47 by sjoerd, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (7)
msg99572 - (view) Author: Sjoerd Mullender (sjoerd) * (Python committer) Date: 2010-02-19 14:47
The mhlib standard library uses the deprecated module multifile.  This causes a warning to be printed whenever mhlib is used.

As a matter of policy, no deprecated features should be used anywhere in the standard library.
msg99573 - (view) Author: Shashwat Anand (l0nwlf) Date: 2010-02-19 15:44
There is a discussion going on python-dev too, the author being sjoerd.
http://mail.python.org/pipermail/python-dev/2010-February/097772.html
GvR reply : http://mail.python.org/pipermail/python-dev/2010-February/097774.html
msg99583 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2010-02-19 16:51
The outcome of that discussion is that what this implies is that there is insufficient test coverage of mhlib, such that no one noticed that mhlib was generating deprecation messages.

mhlib is itself effectively deprecated, since it no longer exists in py3k.  If someone wants to propose patches to fix mhlib that's fine, but this is a very low priority issue.
msg99584 - (view) Author: Sjoerd Mullender (sjoerd) * (Python committer) Date: 2010-02-19 16:58
What's difficult about just doing:

import mhlib

?  That's all it takes to get the warning.
msg99585 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2010-02-19 17:09
Hmm.  Apparently the actual bug is that mhlib itself does not produce a deprecated message.  The test was explicitly changed to mark the module as one that is deprecated.
msg100670 - (view) Author: Sjoerd Mullender (sjoerd) * (Python committer) Date: 2010-03-08 21:46
mhlib is not officially deprecated, if I may believe PEP 4.
Therefore I do not agree with the change that was made to this bug report.
As far as I am concerned, the bug remains that mhlib uses a deprecated module.
msg153845 - (view) Author: Éric Araujo (eric.araujo) * (Python committer) Date: 2012-02-21 03:53
This was fixed by r63030.
History
Date User Action Args
2022-04-11 14:56:57adminsetgithub: 52214
2012-02-21 03:53:03eric.araujosetstatus: open -> closed

versions: - Python 2.6
nosy: + eric.araujo

messages: + msg153845
resolution: fixed
stage: test needed -> resolved
2010-03-08 21:46:46sjoerdsetmessages: + msg100670
2010-02-19 17:09:17r.david.murraysetmessages: + msg99585
title: mhlib uses deprecated module -> mhlib does not emit deprecation warning
2010-02-19 16:58:17sjoerdsetmessages: + msg99584
2010-02-19 16:51:54r.david.murraysetpriority: low
versions: + Python 2.7
nosy: + r.david.murray

messages: + msg99583

stage: test needed
2010-02-19 15:44:06l0nwlfsetnosy: + l0nwlf
messages: + msg99573
2010-02-19 14:47:55sjoerdcreate