-
Notifications
You must be signed in to change notification settings - Fork 259
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
Go To Definition
won't work after updating to the newest Anaconda release
#924
Comments
Go To Definition
won't workGo To Definition
won't work after updating to the newest Anaconda release
Just in case it helps, manually downgrading to Anaconda 2.2.3 fixed the issue |
Same problem for me |
Time to time control + option + g opens new empty tab instead of searching definition |
I'm experiencing the same thing too. |
I will not have time to look into this for a while, I am very busy with other projects right now, if someone steps up to look into this it would be great. |
@DamnWidget Thanks for the heads-up. :) Note, I also experience this issue when jumping within the same file. It seems in that case, it's not the {"success": true, "result": [["__main__.hello", null, 7, 5]], "uid": "df29c0a94da3408e93b1204c9aa7ac74"} |
Something similar happens with "Find Usages", |
quickfix that fixed that for me - change this line: |
@x0nix :) Thank you! This fixes "go to" involving However, navigating within the same file, I still get a blank tab as described here: #924 (comment) — maybe that's another issue. |
x0nix's 'quickfix' only hacks/paves the way to "Goto Definition" of an imported library (at the A quick diff between v2.3.0 and v2.2.3 shows that the problem couldn't reside in those two files alone, Then, there is A. the release notes, https://github.com/DamnWidget/anaconda/releases/tag/v2.3.0
B. the and C. issue #921
| | Short pause to express my total respect to DamnWidget's decision and gratitude for all the past years of their hard work. |> So, do the v2.3.0 "Goto" commands work only with Python >= v3.10 ? Summary of my quick and draft testsWindows/Linux + ST4 + Anaconda-plugin v2.3.0 => 'linting' v3.7 =< Python =< v3.9 code-base None of the v2.3.0 I think a project-developer/project-previous-contributor should step in (code familiarity) or we'll have to wait for someone (including us subscribed to this issue) who has the time or the "talent" ("talent" as in less time/effort). Till then, v2.2.3 is the way backwards for anyone that wants the functionality above (described commands) or just a reassurance that all things work as before (including known quirks and bugs). |
@Gregory-K Thanks for the digging and write-up! Does upgrading to Python 3.10 resolve this? If so, as Sublime plugins as of now run at most on 3.8 (see documentation here), I wonder what workaround @DamnWidget had in mind. |
@mikez the situation is a little perplexed. ST4 provides and 'runs' Python 3.8 for its plugins/plugin-system and will continue to do so till the next major version upgrade, ST5. What DamnWidget is aiming for (at least what I understood by a quick glance at the relevant issues/announcements) is for Anaconda to support the "linting" of Python 3.10 code base. That said, I haven't tried to test it, as all my code for now targets =< Python 3.9. |
Just an update.
I'm attaching some logs and notes. Linux ST4 Console
Windows ST4 JSON DEBUG serverWhen
Further
Just try a
|
So, the problem described in #924 (comment) keeps persisting. Anyone has found a solution to this? Thanks! |
@jrzaurin I'm not aware of a fix yet. It seems @DamnWidget (the maintainer) is prioritizing other projects per #924 (comment) and requested someone look into it. |
hey @mikez Yean I read it. The truth is that this to me is a major drawback 😔. Oh well, maybe I will give VScode a go and hope they fix this soon (I do love Sublime 🙂). Or if anyone knows an Alternative to Amaconda, please let me know. |
@jrzaurin I feel you. I think you may try posting here: https://forum.sublimetext.com/c/ideas-and-feature-requests ... and explain the importance of it. That is, to have Sublime natively support a more powerful "show definition", including imported libraries akin to VSCode. Big thank you to @DamnWidget who has been running this project since 2013. I totally understand if he has less energy and resources for it today. |
@jrzaurin I don't know what your needs, constraints, and workflow are, but you can always downgrade to Anaconda v2.2.3 or try the other LSP alternatives mentioned here https://github.com/DamnWidget/anaconda#alternatives . |
Hi there, I added some alternatives to this plugin a while ago, they can be found in this section of the README file. I am not sure how well they really work, I don't really use ST since circa 2014 so I really couldn't say but they look good to me. Being honest, I didn't archived this repository yet because I still have hopes that someone (or someones) would step up and take care of the project but the possibility seems less probable each day. Good luck everyone! |
@Gregory-K I did try, since I actually wrote this comment #924 (comment). However I found the behaviour rather random in the sense that, sometimes worked, sometimes did not🤷🏻♂️ |
Expected Behaviour
Go to the definition of the object in the source code. For example, when using python for Machine Learning, I cannot access any function in
sklearn
Actual Behaviour
Prints
unable to find 'object'
(see picture attached)Steps to Reproduce
set up an environment with pyenv
install any package (e.g. sklearn)
open sublime and type:
in the editor. Then try: Anaconda -> go to definition
my anaconda user settings look like this:
ST3, Anaconda and OS versions
ST4: 4126
Anaconda version: 2.3.0
MacOS: 12.2.1
ST3 Console Logs
Anaconda's JsonServer Logs
these are the relevant logs I think
The text was updated successfully, but these errors were encountered: