When I am in certain files, for example, External Library files, I am getting this behavior where the Go To Definition command jumps me to the import statement at the top of the file instead of opening the file with the real definition.
For example, I'm in an external library, (jumped here using Go To Definition), and from here, I again want to jump, so I put the cursor on the return statement on the Something token and hit "Go To Definition"....
from package.forme.mod import Something
. . .
. . .
... which jumps me to the "from package.forme.mod import Something" statement at the top of the file. I have the paths and sub-paths defined in External Libraries for the project.
I expect it to instead open the actual definition in the given package/file instead of jumping to the import statement.
Eclipse (Flex Builder 3) version 3.3, but also tried eclipse 3.5 (no flex builder) with same results.
IMPORTANT: My project is mounted on a linux machine. I am using the windows python 2.6 interpreter, but when I actually run my code in linux, it is not the same interpreter (still 2.6). I would guess that shouldn't affect the Go To Definition, but since it might, I wanted to mention it so as to not cause a wild goose chase.