2018.3.0: Pylint: 'F0001:No module named "test.py"' appears in every file with a path that has a space

Since installing the 2018.3.0 version of this extension about an hour ago, I get 'F0001:No module named "test.py"' at the top of every module from pylint (for line 1, character 1), with test.py being replaced with the file’s filename.

This happens even if the file is the only file in its dir. This also only happens with existing VS Code projects, but not new ones.

This is definitely related to this extension and pylint. Because when I copy my project to a new folder, then open it in VSC, these errors disappear. But the original project location still has these errors.

This makes it incredibly difficult to fix on my own, since I don’t know where to look, with regards to VSC. It must be something to do with an internal VS Code database?

Edit: As noted here, this problem only happens with paths with spaces in them. I was able to reproduce this myself.

[amyspark]

I’m getting this error only from projects with spaces in their paths, either new or existing. Can anyone check if this is the case too? (VS Code 1.22.0-insider on Sierra)

[brettcannon]

OK, 2018.3.1 is now live with a fix for this! Sorry everyone for letting this slip out.