New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mhlib does not emit deprecation warning #52214
Comments
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. |
There is a discussion going on python-dev too, the author being sjoerd. |
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. |
What's difficult about just doing: import mhlib ? That's all it takes to get the warning. |
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. |
mhlib is not officially deprecated, if I may believe PEP-4. |
This was fixed by r63030. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: