diff options
| author | Claudiu Popa <pcmanticore@gmail.com> | 2015-12-01 14:58:59 +0200 |
|---|---|---|
| committer | Claudiu Popa <pcmanticore@gmail.com> | 2015-12-01 14:58:59 +0200 |
| commit | 60dc4441f52dcf9d3ffd78b37be304bdce84b87e (patch) | |
| tree | de4b4e93c506b9edceb23d24695c6f0a7b353c3b /ChangeLog | |
| parent | 0b5ab33c81a753ad732bfa5cdcf933bb2167a12c (diff) | |
| download | pylint-60dc4441f52dcf9d3ffd78b37be304bdce84b87e.tar.gz | |
Don't emit import-self and cyclic-import for relative imports of modules with the same name as the package itself.
The problem was partially the fault of astroid.modutils.get_module_part,
in combination with a given context file.
The function returned 'dummy' as the module part for the string
`dummy.dummy.Dummy`, which is in fact true, since the first dummy
is the package and the second dummy is the module from where Dummy
gets loaded. But get_module_part has no way to know this semantic
inference, that the second dummy is a relative import inside the
first one. As such, it's better to just skip the check if the
condition of being relative inside a __init__.py file is found,
since there's no way to load itself in that case.
Closes issues #708 and #706.
Diffstat (limited to 'ChangeLog')
| -rw-r--r-- | ChangeLog | 10 |
1 files changed, 10 insertions, 0 deletions
@@ -22,6 +22,16 @@ ChangeLog for Pylint from other files might leak into the current file, leading to wrong-import-position being emitted by pylint. + * Fix a crash which occurred when old visit methods are encountered + in plugin modules. Closes issue #711. + + * Don't emit import-self and cyclic-import for relative imports + of modules with the same name as the package itself. + Closes issues #708 and #706. + + +2015-11-29 -- 1.5.0 + * Added multiple warnings related to imports. 'wrong-import-order' is emitted when PEP 8 recommendations regarding imports are not respected (that is, standard imports should be followed by third-party |