Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

conda-mode-find-definitions on constant variable points to class, not the def site #435

Open
sangwoo-joh opened this issue Sep 18, 2023 · 0 comments

Comments

@sangwoo-joh
Copy link

sangwoo-joh commented Sep 18, 2023

  • anaconda-mode-server-version: "0.1.15"
  • Emacs version: 28.1
  • Currently using conda-mode from doomemacs (doom version: 7a7503045850ea83f205de6e71e6d886187f4a22)

Description

If I have a constant.py file like below:

CONST_A = 1

, and other module that use this module like below:

from my_package import constant

foo = constant.CONST_A + 1

With this setting, when I call conda-mode-find-definitions on const.CONST_A, it gave me the following:

...
class int:
    @overload
    ....

... which is in anaconda/0.1.15-py3/jedi/third_party/typeshed/stdlib/3/builtins.pyi.

I though it would jump to the actual definition site in constant.py file...
Other definitions, e.g., some user-defined class, go to the proper def-site. Only builtin types gave me strange location.

What should I do to make it give me the actual def-site? Is there any variable to set up?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant