Skip to content
This repository has been archived by the owner on Dec 14, 2021. It is now read-only.

Symbol resolution errors with the latest jedi library #70

Open
midchildan opened this issue Oct 27, 2020 · 4 comments
Open

Symbol resolution errors with the latest jedi library #70

midchildan opened this issue Oct 27, 2020 · 4 comments

Comments

@midchildan
Copy link

This issue has come up while packaging Sourcetrail for NixOS (NixOS/nixpkgs#95530). There seems to be a compatibility problem with recent commits of jedi (davidhalter/jedi@216f976) that prevents the SourcetrailPythonIndexer from resolving symbols from the Python standard library. Though not strictly a bug since we were obviously attempting to use an unsupported configuration, we thought it might be worth creating a issue to avoid problems when the next version of jedi is released.

Here's a screenshot with the errors:
Screenshot from 2020-10-27 22-11-25

@mlangkabel
Copy link
Contributor

Thanks for the heads up. Are you indexing Python 2 code? Or is it Python 3?

@midchildan
Copy link
Author

I’ve indexed the sample project included in Sourcetrail with Python 3.8.

@matejak
Copy link

matejak commented Oct 29, 2020

I get this error as well on Archlinux, and I suspect that #52 is of the same kind - what I experience is that occasionally symbols from the standard library are not resolved, and restarting the scan can help.
I wouldn't say that it is a brand new issue - I experience this kind of behavior already for a couple of months.

@midchildan
Copy link
Author

I wouldn't say that it is a brand new issue - I experience this kind of behavior already for a couple of months.

I think this is a separate issue because no amount of restarting helped. Since downgrading jedi did fix the issue however, I see it likely that it is a problem introduced by recent commits from jedi.

# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants