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.
Linter stays half-dead on Windows
See original GitHub issuedemo.mp4 No clue how to reproduce, it’s a first; other spyder instance is running a TensorFlow session. Linter does detect #TODO and unused imports, but not syntax errors, and code folding fails. Kernel restart, Spyder restart, Anaconda Powershell Prompt restart didn’t help - didn’t try restarting computer, but think it’ll work.
Problems: (reproduced in 4.1.2)
- Syntax error red flag persists after fixing the error1
- Syntax errors no longer detected
- Unused variables no longer detected
- Code folding markers misplaced4
- Code folding folds only partially5
1: This is usually the first ‘symptom’; everything goes downhill from there. The red flags can be dismissed by cut-repasting the entire code in the file.
4:
5:
Issue Analytics
- State:
- Created 4 years ago
- Comments:26 (26 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@OverLordGoldDragon, thanks a lot for giving us a reproducible example!! That’s all we needed!
After hours of debugging I finally found the cause (it was Windows specific). Right now I’m preparing a pull request and the fix will be available in our 4.1.4 version (to be released in mid June).
Thanks for the pointer @OverLordGoldDragon! I confirmed this generates an internal error in Jedi, which probably kills the linter afterwards on Windows (that’s not the case on Linux, which is my main OS).
I’ll test on Windows later on to check if that’s the case.