Closed aphearin closed 5 years ago
The only thing we changed here afaik is that we now show such errors. Before we only logged them to the Sublime console.
So I think it didn't work before but you never noticed. 🤔
Ok, then maybe this is innocuous. Is it easy to change the display settings to hide this error message?
Hm, 'innocuous'. I think when you see such an error, the linting doesn't work, so you either fix that. (E.g. import configparser
indicates that you run the python3 flake8, it errs bc you run in a python27 environment which doesn't have configparser
(but ConfigParser
LOL)).
If you don't want to fix it (right now), it is better to just disable the plugin/linter per project or globally, bc always trying to run flake8 just eats cpu cycles.
Closing due to age
A recent update of sublime seems to have caused a problem for my flake8 plugin configuration. I am not sure which update caused this behavior, but it must have been within the past few days. When viewing python modules with SublimeLinter turned on, I now get the following error message: