improvement: fallback to jedi interpeter in completion

[akshayka]

This change improves the responsiveness and coverage of code completion.

• Fallback to the Jedi Interpreter class when static analysis-based completion turns up empty. (Jedi's static completer fails on some libraries, like ibis.) The Interpreter completer evaluates code, so care is taken to avoid race conditions with the kernel by introducing a lock on the globals dictionary. Acquiring/releasing the lock works in Pyodide, even though Pyodide doesn't support creating threads, so no separate codepath was needed for WASM.
• Decrease the docstring limit when running locally from 1000 to 80.
• Add a cumulative timeout across completions, after which we stop computing completion info.

As a result:

• We now get completions for Ibis, and probably other libraries that we were failing to complete.
• Pandas and NumPy completions are much faster (due to the docstring limit / timeout); previously, they were so slow as to not really work at all.

Note: While the Interpreter completer is running, the user won't be able to run code / the kernel won't process control requests. For this reason the Interpreter completer has a timeout of 1 second (we can make this even lower if needed). In practice I believe this won't be a problem since the Interpreter completer is only a fallback.

Tested: manually, by playing with a notebook that uses Ibis, Pandas, and NumPy locally.

In the future, we could make docstring fetching lazy, in which case we could remove the docstring limit.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
marimo-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 5, 2024 11:47pm
marimo-storybook	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 5, 2024 11:47pm

[github-actions]

🚀 Development release published. You may be able to view the changes at https://marimo.app?v=0.6.17-dev1