Skip to content
This repository was archived by the owner on Apr 14, 2022. It is now read-only.
This repository was archived by the owner on Apr 14, 2022. It is now read-only.

'Go to Definition' for relative imports not resolving directly to the appropriate module #24

Description

Let's say I have pkg and pkg.subpkg, both packages. I also have pkg.mod and pkg.subpkg.submod, both modules. If I do from .. import mod from within pkg.subpkg.submode I get asked which package to resolve to -- pkg/__init__.py or pkg/mod.py -- even though pkg.__init__ is empty. I would expect the lack of ambiguity to not ask me which package to resolve to.

Attached are the test files I was using.
pkg.zip

Activity

  1. MikhailArkhipov commented on Feb 8, 2019

    @MikhailArkhipov

    To verify with #546

  2. added a commit that references this issue on Mar 5, 2019
    8b2edb2
  3. added a commit that references this issue on Nov 1, 2019
    0869eb3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions