Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Code analysis fails with `No module named pylint` on pip based installation
See original GitHub issueDescription
What steps will reproduce the problem?
Just open spyder, open a file, and click for code analysis in the GUI
Traceback
pylint error:
C:\Program Files\Python310\pythonw.exe: No module named pylint
Versions
- Spyder version: 5.3.3 (pip)
- Python version: 3.10.7 64-bit
- Qt version: 5.15.2
- PyQt5 version: 5.15.5
- Operating System: Windows 10
Dependencies
# Mandatory:
atomicwrites >=1.2.0 : 1.4.1 (OK)
chardet >=2.0.0 : 5.0.0 (OK)
cloudpickle >=0.5.0 : 2.1.0 (OK)
cookiecutter >=1.6.0 : 1.7.3 (OK)
diff_match_patch >=20181111 : 20200713 (OK)
intervaltree >=3.0.2 : 3.1.0 (OK)
IPython >=7.31.1;<8.0.0 : 7.34.0 (OK)
jedi >=0.17.2;<0.19.0 : 0.18.1 (OK)
jellyfish >=0.7 : 0.9.0 (OK)
jsonschema >=3.2.0 : 4.6.0 (OK)
keyring >=17.0.0 : 23.5.0 (OK)
nbconvert >=4.0 : 6.5.0 (OK)
numpydoc >=0.6.0 : 1.2 (OK)
paramiko >=2.4.0 : 2.11.0 (OK)
parso >=0.7.0;<0.9.0 : 0.8.3 (OK)
pexpect >=4.4.0 : 4.8.0 (OK)
pickleshare >=0.4 : 0.7.5 (OK)
psutil >=5.3 : 5.9.2 (OK)
pygments >=2.0 : 2.12.0 (OK)
pylint >=2.5.0;<3.0 : 2.15.2 (OK)
pyls_spyder >=0.4.0 : 0.4.0 (OK)
pylsp >=1.5.0;<1.6.0 : 1.5.0 (OK)
pylsp_black >=1.2.0 : 1.2.0 (OK)
qdarkstyle >=3.0.2;<3.1.0 : 3.0.3 (OK)
qstylizer >=0.1.10 : 0.2.1 (OK)
qtawesome >=1.0.2 : 1.0.3 (OK)
qtconsole >=5.3.2;<5.4.0 : 5.3.2 (OK)
qtpy >=2.1.0 : 2.1.0 (OK)
rtree >=0.9.7 : 1.0.0 (OK)
setuptools >=49.6.0 : 65.3.0 (OK)
sphinx >=0.6.6 : 5.1.1 (OK)
spyder_kernels >=2.3.3;<2.4.0 : 2.3.3 (OK)
textdistance >=4.2.0 : 4.4.0 (OK)
three_merge >=0.1.1 : 0.1.1 (OK)
watchdog >=0.10.3 : 2.1.9 (OK)
zmq >=22.1.0 : 23.2.1 (OK)
# Optional:
cython >=0.21 : 0.29.32 (OK)
matplotlib >=3.0.0 : 3.5.3 (OK)
numpy >=1.7 : 1.23.3 (OK)
pandas >=1.1.1 : 1.4.4 (OK)
scipy >=0.17.0 : 1.9.1 (OK)
sympy >=0.7.3 : 1.11.1 (OK)
Issue Analytics
- State:
- Created a year ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
pylint fails with F0001: No module named __init__.py (fatal ...
pylint --help-msg=F0001 :fatal (F0001): Used when an error occurred preventing the analysis of a module (unable to find it for instance).
Read more >Linting Python in Visual Studio Code
The linter has not been installed in the current Python environment. Open a command prompt, navigate to the location where your selecter interpreter...
Read more >Pylint - PyPI
Pylint is a static code analyser for Python 2 or 3. The latest version supports Python 3.7.2 and above. Pylint analyses your code...
Read more >Unable to import django urls pylint import error - miocittadino.it
No name 'QApplication' in module 'PyQt5 QtWidgets' Error in Pylint ... Step 1) Create a file and name it test. install python analyzer...
Read more >Frequently Asked Questions - Pylint 2.16.0-dev documentation
pip install pylint ... How do I find the name corresponding to a specific command line option?# ... Pylint gave my code a...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi,
Yes: it works now! I can run it and see in the pane the results of pylint
Thank you
Maybe the env var missing to add in the process Spyder launches is
APPDATA🤔Could you try to add the following code around line 374 of the file I referenced above? :
processEnvironment.insert("APPDATA", os.environ.get("APPDATA") )