-
Notifications
You must be signed in to change notification settings - Fork 48
for specific file pylint works but linter-pylint doesn't -- Column start greater than line length #235
Comments
similar error, affecting all my files
|
@mbdevpl That looks like a pylint issue. Can you reproduce it using the latest pylint (1.8.1) ? |
@ddaanet thanks, I did apply the PR manually and it fixed my issue. |
Well, with pylint 1.8.1 and my configuration I initially get a different error - as reported by @djsly . After I temporarily rename my E.g. on latest revision mbdevpl/version-query@7ebfe39, with the same file
|
Sorry, I didn't mention you above - @ddaanet .
For me this being a pylint issue is highly unlikely, because as I wrote pylint by itself runs ok. |
@mbdevpl as mentioned by @djsly, the error he reported has a fix merged Regarding your specific problem: this is intriguing. Googling for your error message quickly gives this: So my guess is the problem comes from Still looks like a pylint bug to me. |
@mbdevpl You can either determine where |
@Arcanemagus @ddaanet Indeed, I was in the wrong, pylint reports error location outside of existing code! I've created an issue pylint-dev/pylint#1839, hopefully it will be resolved. The examples for reproduction is posted there and already here too. Strictly speaking pylint is reporting wrong column - line number is correct. When I modify code just a little bit (in an unrelated location) the reported column changes to the correct value. A very strange bug... If you're interested, please see details there. In the meantime, since it happens from time to time that linting tools report invalid locations, wouldn't it be a good idea to either:
and issue some warning instead of just crashing? |
I think the idea here is to inconvenience users so the linters get fixed, so in the end everyone get better linters. I mean, now you have reported an issue to pylint. Which will probably be fixed soon. If linter-pylint were more lenient, would you have reported the issue? Probably not. |
Note that that:
It's missing:
|
I get a similar error sometimes when mirroring a file with "Split Right"
atom 1.34.0 |
hi Gets i got similar issue any advice please, keep scratching my head /Users/amroalfadil/.atom/packages/linter/lib/linter-registry.js:154 [Linter] Error running Pylint Error: Column start (72) greater than line length (18) for line 1 /Users/a/.atom/packages/linter/lib/linter-registry.js:154 [Linter] Error running Pylint Error: Column start (8) greater than line length (7) for line 0 |
The issue I'm having recently is that for a file: https://github.com/mbdevpl/version-query/blob/master/version_query/version.py linter-pylint is always failing, since I installed it not so long ago.
For latest as of now revision https://github.com/mbdevpl/version-query/blob/8289045e7b818aa36a447202cdb3b46d6207c9a1/version_query/version.py the error message reads:
However pylint itself works (e.g. on my MacBook):
... and further logs showing that pylint works for that file can be found on TravisCI, e.g Python 3.6 on Linux: https://travis-ci.org/mbdevpl/version-query/jobs/294048400#L1154
Similar issues in the past were #2 and #165 - it seems this might not be related to any of them though.
Error always happens for me with linter-pylint 2.1.0 (latest, no updates available) on Mac and Linux.
And BTW, linter-pylint works great for all my other files, I think it's a really useful and good tool overall. What can I do to help fix this one annoying error?
The text was updated successfully, but these errors were encountered: