+1 In addition to the above arguments, there are two other advantages (but which do not justify deactivating jedi tab completion for sage-9.3):
- It's noticably faster without jedi. - Keywords of functions appear first in the list, where they belong and not somewhere hidden. (Deactivating jedi as above, I can tab complete `polytopes.cube(` and immediatily see the two available keywords). Jonathan vdelecroix schrieb am Samstag, 10. April 2021 um 22:30:13 UTC+2: > Dear all, > > This message is an emergency call to deactivate jedi before sage-9.3. > > I had a recent post about tab-completion crashing sage. It involved > external libraries and could be somehow considered as minor. Here are > two more serious issues > > 1. If you tab-complete "s" with in Sage twice it will crash Sage > (see details in https://trac.sagemath.org/ticket/31632#comment:22) > > 2. If you tab-complete then all lazy import that starts with the > prefix are resolved > (see for example https://trac.sagemath.org/ticket/31632#comment:16) > > Actually, number 1 is a consequence of number 2 and the underlying > problem is tracked at https://trac.sagemath.org/ticket/31643. > > There is an easy way to go which consists in turning off jedi (and > fall back to the internal IPython completer). All problems above > will be avoided. You can test it yourself with > > sage: from IPython import get_ipython > sage: ip = get_ipython() > sage: ip.Completer.use_jedi = False > > Could that be done? I am welcoming any other suggestion. > > Best > Vincent > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/cd63a75a-3a5c-4467-ac3c-e2ae5ef26aafn%40googlegroups.com.
