[Bug 190542] Re: Problem with Pylint's handling on __all__
Pander
190542 at bugs.launchpad.net
Thu May 12 21:53:37 UTC 2016
** Changed in: pylint (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to pylint in Ubuntu.
https://bugs.launchpad.net/bugs/190542
Title:
Problem with Pylint's handling on __all__
Status in pylint package in Ubuntu:
Invalid
Bug description:
Binary package hint: pylint
The following example code illustrates two surprises with Pylint's handling of __all__.
1. Including an nonexistant member should raise an error.
2. republishing an imported member in __all__ should not raise a warning that the import was unused.
"""Test Pylint's use of __all__.
* NonExistant is not defined in this module, and it is listed in
__all__. An error is expected.
* This module imports path and republished it in __all__. No errors
are expected.
"""
from os import path
__all__ = [
'Dummy',
'NonExistant',
'path',]
class Dummy:
"""A class defined in this module."""
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pylint/+bug/190542/+subscriptions
More information about the foundations-bugs
mailing list