-
-
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
test_do_not_import_files_from_local_directory fails with trying to import "completely_unknown" #3636
Closed
bnavigator opened this issue
May 19, 2020
· 1 comment
· Fixed by #4153, tingvarsson/telegram.ongabot#33, hypothesis/checkmate#227 or freelawproject/courtlistener#1620
Closed
test_do_not_import_files_from_local_directory fails with trying to import "completely_unknown" #3636
bnavigator opened this issue
May 19, 2020
· 1 comment
· Fixed by #4153, tingvarsson/telegram.ongabot#33, hypothesis/checkmate#227 or freelawproject/courtlistener#1620
Comments
Ha! Found it. PYTHONPATH is set by the |
sbraz
added a commit
to sbraz/pylint
that referenced
this issue
Feb 28, 2021
51c646b only stripped the first bad sys.path entry, causing problems when PYTHONPATH starts or ends with a colon.
sbraz
added a commit
to sbraz/pylint
that referenced
this issue
Feb 28, 2021
51c646b only stripped the first bad sys.path entry, causing problems when PYTHONPATH starts or ends with a colon.
sbraz
added a commit
to sbraz/pylint
that referenced
this issue
Feb 28, 2021
51c646b only stripped the first bad sys.path entry, causing problems when PYTHONPATH starts or ends with a colon. Closes: pylint-dev#3636
sbraz
added a commit
to sbraz/pylint
that referenced
this issue
Feb 28, 2021
51c646b only stripped the first bad sys.path entry, causing problems when PYTHONPATH starts or ends with a colon. Closes: pylint-dev#3636
sbraz
added a commit
to sbraz/pylint
that referenced
this issue
Feb 28, 2021
51c646b only stripped the first bad sys.path entry, causing problems when PYTHONPATH starts or ends with a colon. Closes: pylint-dev#3636
sbraz
added a commit
to sbraz/pylint
that referenced
this issue
Feb 28, 2021
51c646b only stripped the first bad sys.path entry, causing problems when PYTHONPATH starts or ends with a colon. Closes: pylint-dev#3636
4 tasks
Pierre-Sassoulas
pushed a commit
that referenced
this issue
Feb 28, 2021
This was referenced Mar 1, 2021
Merged
This was referenced Mar 15, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
(Same environment as in #3635)
Trying to update the openSUSE package for pylint:
What could cause the undesired import? If I chroot into the build environment and call
python3 -m pylint astroid.py
, I get the sameModuleNotFoundError
.But if I install the package onto a live openSUSE Tumbleweed system and execute the same call, the import does not happen.
Package versions:
python3-astroid-2.4.1
python3-isort-4.3.21
python3-mccabe-0.6.1
python3-toml-0.10.0
For the full environment, see the build log as linked above.
The text was updated successfully, but these errors were encountered: