-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Cannot find module if source file is a symbolic link #1470
Comments
Fix pylint errors for version 1.7.1: * Do not use `len(SEQUENCE)` as condition value * Unnecessary "else" after "return" Version 1.7.1 cannot yet be made the default for Travis, as this version cannot handle the way we install out Python module using symbolic links (pylint-dev/pylint#1470).
Fix pylint errors for version 1.7.1: * Do not use `len(SEQUENCE)` as condition value * Unnecessary "else" after "return" Version 1.7.1 cannot yet be made the default for Travis, as this version cannot handle the way we install out Python module using symbolic links (pylint-dev/pylint#1470).
Fix pylint errors for version 1.7.1: * Do not use `len(SEQUENCE)` as condition value * Unnecessary "else" after "return" Version 1.7.1 cannot yet be made the default for Travis, as this version cannot handle the way we install out Python module using symbolic links (pylint-dev/pylint#1470).
Fix pylint errors for version 1.7.1: * Do not use `len(SEQUENCE)` as condition value * Unnecessary "else" after "return" Version 1.7.1 cannot yet be made the default for Travis, as this version cannot handle the way we install out Python module using symbolic links (pylint-dev/pylint#1470).
I think this is related to the change made in pylint-dev/astroid@cda9dc4 I'm getting the same problem when one of my python modules is actually a symlink, on macOS High Sierra, Python 2.7.14 I changed modutils.py line 290 back to what it was before cda9dc4, and that fixed the problem of Pylint not being able to find the symlink.
|
Any fix for this in the meantime? (in particular, should I check with astroid if we can help fix there?) |
Increase the minimal required version as older versions have a problem with newer numpy versions. Additionally, the new pylint version has a problem with symlinks (pylint-dev/pylint#1470). Therefore, run the pylint test directly on the source code and not on the build folder.
This is still a bug right? |
@Pluckerpluck I presume so, the issue hasn't been closed or worked on lately. |
@Pluckerpluck I am also faced with this issue for pylint 2.3.1. |
This seems to be an issue with the latest version of pylint:
Symlinks and pylint worked fine for our team on pylint 2.4.x |
This is a regression test for pylint-dev/astroid#1253 Closes #1470
This is a regression test for pylint-dev/astroid#1253 Closes #1470
This is a regression test for pylint-dev/astroid#1253 Closes #1470
Closes pylint-dev#1470 Closes pylint-dev#3499 Closes pylint-dev#4302 Closes pylint-dev#4798 Closes pylint-dev#5081
This is a regression test for pylint-dev/astroid#1253 Closes pylint-dev#1470
Somewhere between versions 1.5.5 and 1.7.1 the behaviour concerning modules using symbolic links to install files in the module directory has changed. Running
pylint
on such a module gives the following error:Steps to reproduce
Consider the following directory structure:
with
__init__.py
containing:and
_func.py
containing:The directory
/tmp/yyy/py/install/pyLib
is included in the environment variablePYTHONPATH
. Importing the modulepyMyTool
in Python works and has the expected result:Current behavior
Running
pylint pyMyTool
prints the aforementioned error message.Expected behavior
Running
pylint pyMyTool
should run its tests.pylint --version output
Please let me know in case you need additional information.
The text was updated successfully, but these errors were encountered: