atom-community / atom-community/ide-python
Unable to goto definitions in __init__.py
- Dominant language
- JavaScript
- Stars
- 238
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Here is my reproduction project:
```shell
fjompo@grande repro$ find .
.
./foo
./foo/__init__.py
./foo/bar.py
./foo/baz.py
fjompo@grande repro$ cat foo/__init__.py
test = 5
fjompo@grande repro$ cat foo/bar.py
from . import test
from .baz import test2
print(test)
print(test2)
fjompo@grande repro$ cat foo/baz.py
test2 = 42
fjompo@grande repro$ python -m foo.bar
5
42
```
If i go to `foo/bar.py` and highlight `test2`, then go-to-definition works, but for `test` it does not. It simply yields _"Sorry, no definitions found."_
This is likely not an issue with jedi, as shown here:
```python
>>> import jedi
>>> jedi.Script(None, path="foo/bar.py").goto(line=3, column=7, follow_imports=True)[0].module_path
PosixPath('/home/fjompo/tmp/repro/foo/__init__.py')
>>> jedi.Script(None, path="foo/bar.py").goto(line=4, column=7, follow_imports=True)[0].module_path
PosixPath('/home/fjompo/tmp/repro/foo/baz.py')
```
Here are the project files: [repro.zip](https://github.com/atom-community/ide-python/files/8044900/repro.zip)
Contributor guide
Research direction
Reproduce the problem with foo/__init__.py, foo/bar.py, and foo/baz.py, then compare Atom's go-to-definition behavior with the shown jedi.Script.goto calls. Start from the integration entry point that handles definitions for Python imports. Done means selecting test in foo/bar.py opens foo/__init__.py, while test2 continues to open foo/baz.py.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, python
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100