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.

pylint errors stay around after deleting code file in working copy

See original GitHub issue

VSCode Version: 1.23.1
OS Version: Win 10 1803
Extension Version: 1.29.0
System Language: English
SVN Version: TortoiseSVN 1.10.0 svn, version 1.10.0-dev (under development) compiled Apr 14 2018, 10:24:15 on x86-microsoft-windows

Issue

After deleting some bug.py, pylint errors for bug.py stay around. I could repro this with python and with latex files. I have reported https://github.com/Microsoft/vscode/issues/49187 yet I am told this has to do with extensions. I have reported https://github.com/Microsoft/vscode-python/issues/1235 but am told they cannot reproduce.

Steps to Reproduce

In Windows Explorer:

Create folder “Repo” somewhere
Using TortoiseSVN, “create repository here”
Create folder “Work” somewhere
Checkout from “Repo”

In VS Code:

Install Python extension
Using Ctrl-K-O, open “Work”
Ctrl-N, type “öäü”, Ctrl-S, save as “bug.py”
Click the “(x) 1 /!\ 0” in the status bar (bottom left) to open “Problems”. Note the problem (undefined variable öäü).
Right-click “bug.py” in “Work”, Delete
Note the problem sticks around.

SVN Output

Using svn "svn, version 1.10.0-dev (under development)" from "C:\Program Files\TortoiseSVN\bin\svn.exe"
[xyz]$ svn info --xml
[xyz]$ svn stat --xml --no-ignore --ignore-externals
[xyz]$ svn info --xml
[xyz]$ svn log -r BASE:HEAD -q --xml
[xyz]$ svn stat --xml --no-ignore --ignore-externals
[xyz]$ svn cat bug.py
svn: warning: W200005: 'C:\Src\xyz\bug.py' is not under version control
svn: E200009: Could not cat all targets because some targets are not versioned
svn: E200009: Illegal target for the requested operation

[xyz]$ svn stat --xml --no-ignore --ignore-externals
[xyz]$ svn stat --xml --no-ignore --ignore-externals

Issue Analytics

State:
Created 5 years ago
Comments:7 (5 by maintainers)

Top GitHub Comments

1reaction

bersbersberscommented, Jun 11, 2018

Looks good to me, thanks so much!

0reactions

JohnstonCodecommented, Jun 9, 2018

No that PR was to fix a duplication bug. I should be able to fix it by changing the uri scheme just need to see where I use it in the codebase

Top Results From Across the Web

pylint errors stay around after deleting code file #1235 - GitHub

After deleting bug.py, pylint errors for bug.py are discarded. (This works for .cpp files, for example.) Steps to reproduce: Create bug.py; Write anything...

Disable errors in .pylintrc doesn't work in VS Code

For this, use the command line: cd into the directory in question and run pylint in verbose mode: pylint --verbose . This shows...

Pylint Errors | Improve Your Code with Pylint and Black

Pylint will first look in the current working directory for a .pylintrc to use. That is why it's easiest to copy the file...

Pylint Documentation - Read the Docs

Pylint is a tool that checks for errors in Python code, tries to enforce a coding standard and looks for code smells. It....

A curated list of pylint errors with explanation and examples

A curated list of pylint errors with explanation and examples.