You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 14, 2022. It is now read-only.
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.
…ng directly to the appropriate module (microsoft#702)
* Fixmicrosoft#24: 'Go to Definition' for relative imports not resolving directly to the appropriate module
* Add test
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Let's say I have
pkg
andpkg.subpkg
, both packages. I also havepkg.mod
andpkg.subpkg.submod
, both modules. If I dofrom .. import mod
from withinpkg.subpkg.submode
I get asked which package to resolve to --pkg/__init__.py
orpkg/mod.py
-- even thoughpkg.__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
The text was updated successfully, but these errors were encountered: