Open TigorC opened 11 years ago
I also filed this against SublimeLinter, since it seems to be their bug. It looks pretty sure to me that it was introduced in 1.6.13. I've reverted to 1.6.12 for now.
Hi @glyph
Reverting to SublimeLinter 1.6.12 fixed the problem?
@DamnWidget Yes.
Seems that they update PyFlakes (3 times) and PEP8 linters but I didn't see any change that can affect ast module in a global way (no monkeypatching) I am going to spend some time investigating this on the weekend.
Regards.
is there any progress on this bug? Working without sublime linter is super painful.
@NorthIsUp Reverting to SublimeLinter 1.6.12 is probably easiest for now. I've done that everywhere and things are working fine; 1.6.13 didn't add any new features I needed, at least.
I just upgraded to SublimeLinter 1.7.0 and it looks like the problem is fixed. At least, the few "go to definition" executions I tried seem to work. Updated the bug there as well. If others can verify, this should be closed.
I also updated to version 1.7 "go to definition" does not work. Now, instead of "SublimeLinter" I use Pep8lint (https://github.com/dreadatour/Pep8Lint)
So, removing Sublime Linter fixes "Go To Definition" for you?
Yes
SublimeRope and SublimeLinter 1.6.13. "Go to definition" not work.