Dave Halter

That sounds great. If it's using parso already would it be possible to just push it into Jedi? At the moment the problem is mostly that Jedi doesn't really work...

> The only two parts that use parso are for determing what names are already in a file and if a completion should be suggested. The majority of the code...

> Would it be possible to move autoimport to its own package so both rope and jedi can use it? I'm not sure. Since Jedi already uses parso and manages...

You are probably right about persistence. I'm also not sure if my approach would even be feasible. I have very good approaches for Rust, but there it's easier to structure...

Yeah, I guess sqlite3 is probably fine to have as an index, as long as invalidation works properly.

This is originally a numpy issue (though Jedi could do a bit better): ``` >>> import inspect >>> inspect.signature(np.random.uniform) Traceback (most recent call last): File "", line 1, in File...

I feel like Jedi doesn't do very weird stuff. AFAIK it uses `__import__`. My feeling is that this is a `paddle` issue.

Requires https://github.com/davidhalter/parso/issues/138

@pappasam Can you maybe clarify which functionality this is about? I have no idea what tooltips are in VSCode/LSP or your server and how that relates to the Jedi API.

Isn't there some option to provide a path from vscode? Jedi can deal with venvs just fine, but you need to tell it where to scan for them or give...