-
Notifications
You must be signed in to change notification settings - Fork 144
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
bash_kernel bug with readline > v8.0 in conda environments #115
Comments
could be related to #107 try with
Does someone know why this problem exists in |
That does look like it might be related to bracketed paste. At a guess, bash is sending the escape codes to switch bracketed paste mode on & off, but Jupyter's limited terminal emulation doesn't support them, so they both show up and interfere with checking exit codes. Disabling bracketed paste mode is probably a good idea. With bash_kernel, you can't paste anything directly into the bash session anyway (it's running behind the Jupyter machinery), so there's no need for it. I think the right place to fix it is this file in pexpect, if anyone wants to make a PR. |
Thanks, this does fix the problem (temporarily) for the duration of each session! |
@CriticalSci Please see my comment in #117 (comment) for a hack that could help the workaround to 'stick' for all Bash kernel notebooks. |
I think #120 should fix this. |
When accessing this kernel in a conda environment containing
readline
v8.1 (as is the default inconda-forge
ordefaults
channels) every command output returns garbled with exit status 1 in the Jupyter notebook.Only readline v8 (the default in the anaconda channel) restores normal behaviour.
Note the Jupyter lab server is also running nb_conda_kernels to access kernels across conda environments.
Can anyone advise what could be the problem here? Is there something in readline 8.1 breaking the code? Or is this specific to my setup?
The problematic environment configuration arises with anything other than anaconda as top priority channel:
The text was updated successfully, but these errors were encountered: