-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Autocomplete repeats content already in the cell. #6709
Comments
Hi @tillahoffmann, thank you for submitting this issue. Would it be possible for you to try downgrading your current version of |
Restricting ipython<8.6 appears to do the trick (see below for a locked requirements.txt), thank you! Do yo know why >=8.6 affects the autocomplete? requirements.txt locked with pip-compile
|
Hi @tillahoffmann thank you for getting back on this one. I've suggested downgrading IPython in our triage meeting because there was a substantial refactor of completer in the recent versions (ipython/ipython#13745, ipython/ipython#13852). The issue you see looks like an edge case when If you are interested in why, see: ipython/ipython#13935 (comment) |
Thanks for the additional context, @krassowski. I did indeed disable jedi because autocompletion was quite slow for me with jedi enabled. I'll keep the downgraded version of ipython for now and/or try enabling jedi again until ipython/ipython#13943 is included in a release. Thanks again. |
When I use autocomplete, the content that is already in the cell is repeated. The following video probably is the most clear description of the issue. I would have expected only the content after the
.
to be inserted.Screen.Recording.2023-02-03.at.16.13.50.mov
Desktop (please complete the following information):
I've used a clean virtualenv with python 3.10.0 configured with pyenv and pyenv-virtualenv installed with brew. I've removed
~/.jupyter
just in case of a funky configuration. I've tried different versions of the notebook package with the same results: 6.5.2 and 7.0.0a11. I'm observing the same issue with jupyterlab==4.0.0a33.I can not reproduce this issue if I run the notebook in a docker container with the following Dockerfile.
Some more details below.
The text was updated successfully, but these errors were encountered: