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
SublimeLinter: #4 pylint <untitled 42> ERROR #62
Comments
Hi! That's a hard crash of pylint itself. Check if you're running the newest version maybe. (In the traceback you see some paths. Are these correct, t.i. are you running the latest python just on c:/python? Or have you multiple pythons installed and we're picking an old one?) |
Hi @kaste Python and pylint are the latest (stable) versions. I've removed other version from the system prior to testing. If I save the file first, before changing the syntax to Python (either automatically with providing a file extension
I've now created a small test file to check for common linting issues / errors:
The linting output I now get is this message:
The message is consistent with the Windows command line output, so SublimeLinter-pylint is doing just fine:
Working with an unsaved file is an edge case IMHO, so I would consider this issue as closed: |
Hm. Actually, this plugin here is configured to not run on dirty buffers/views. And we take it for granted that untitled/new buffers are always dirty. So I need to check this. Do the tabs show the dirty/unsaved dot and still are crashing? |
I can see a tiny issue here, although I cannot reproduce the brash/bug. For example, for an untitled file we might call
(note the |
Interesting! I did a bit of testing and from what I've seen so far: The issue occurs when creating a new untitled file (no content yet) and then setting the syntax to Python. The issue doesn't occur, if a new untitled file is created, content added (anything, really) and then set to be of type Python. Is it possible that Sublime doesn't allocated any buffer/memory for a new unsaved file, when the file has been "created" (new untitled file) but no content has been added or the (empty) file been saved first? |
Sublime does some special casing here for sure but you also just found an edge case bug. 💪 I've created a ticket in SublimeLinter core. Probably easy to fix. |
Thanks for filing SublimeLinter/SublimeLinter#1761 (comment) . |
In times of Corona I like it to stay open, it will get closed if a patch lands in core SublimeLinter. |
Hello,
I have issues with using SublimeLinter-pylint, the linting is not working.
Unfortunately, I get an error message.
Steps to reproduce: I've installed all required software and packages
then opened a new document, changed the syntax to Python and
typed "print". Then this error was visible in the Sublime Text terminal:
Versions:
Python and Pylint are accessible via PATH variable system-wide:
Sublime Text 3 console output is:
Is there anything I can try to troubleshoot?
Chris
The text was updated successfully, but these errors were encountered: