Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provisional Completer API Thoughts #13155

Closed
jdtsmith opened this issue Sep 23, 2021 · 0 comments · Fixed by #13745
Closed

Provisional Completer API Thoughts #13155

jdtsmith opened this issue Sep 23, 2021 · 0 comments · Fixed by #13745

Comments

@jdtsmith
Copy link
Contributor

I've been using the provisional completion API for an Emacs mode targeting inferior-iPython. The docs mention interest in feedback on the API, so I thought to open an issue to discuss. Some thoughts and suggestions:

  • The current provisional API was put in place 5 years ago. Are there any plans to change it in the near term? If not, perhaps the provisional context requirement should be dropped, and the docs should no longer indicate the functionality as experimental. After all, [Tab] has been providing these completions for 5 years, so they are pretty well vetted!
  • It's very useful that the completion API provides the bounds of the string which it is completing. What would also be very helpful is to also get the bounds of the full expression iPython + jedi are evaluating for the completion itself. For example, in x.y[0].z[Tab] IPCompleter will indicate z as the completion text to alter, but presumably iPython knows that it's evaluating an entire expression x.y[0].z___. This would be very useful for users of the API that want to query functions for docstrings, etc. during completion.

Thanks for iPython.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant