search

CoatiSoftware / SourcetrailPythonIndexer

Python Indexer for Sourcetrail based on jedi, parso and SourcetrailDB
GNU General Public License v3.0
90 stars 28 forks source link

Symbol resolution errors with the latest jedi library #70

Open midchildan opened 3 years ago

midchildan commented 3 years ago

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 (https://github.com/davidhalter/jedi/commit/216f976fd5cab7a460e5d287e853d11759251e52) 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 commented 3 years ago

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

midchildan commented 3 years ago

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

matejak commented 3 years ago

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 commented 3 years ago

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.