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
ipython 8.2.0 mixing history from multiple ipython sessions #13631
Comments
I have just checked that this was caused by the #13592 as the problem didn't occur before it. |
Hi |
This issue is indeed very inconvenient. I'm not sure the current behaviour is ever desirable. |
It forces get_tail to put the current session last in the returned results.
It forces get_tail to put the current session last in the returned results.
This fixed the mixing of multiple history seen in #13631
closed by #13657 |
I'm still experiencing this issue on: IPython 8.5.0 (and the versions all the way down to 8.2.0, inclusive), and Python 3.8.5. |
@hristog Can confirm, seeing the same on IPython 8.5.0:
|
Thanks for reproducing and confirming the issue, @harenbrs! |
same with IPython 8.6.0, fixed it by updating old promt_toolkit (3.0.5) to the latest one (3.0.32) |
Hi,
After updating to ipython 8.2.0 I observe a very annoying behaviour, when pressing 'UP_ARROW' in long running ipython session brings not the previous command from history, but a command from some other ipython session running concurrently.
How to reproduce.
This is very inconvenient behaviour that completely breaks the workflow in long running ipython sessions. I assume it must be a regression.
Thank you.
(I'm using python 3.8 with the latest prompt-toolkit 3.0.29 on linux (ubuntu 18.04)
The text was updated successfully, but these errors were encountered: