Open orlitzky opened 2 years ago
I've never seen this one. Is this a regression introduced by the most recent IPython upgrade?
Replying to @mkoeppe:
I've never seen this one. Is this a regression introduced by the most recent IPython upgrade?
It seems the file is only locked during the execution of a statement. So if you run a long computation in one terminal, e.g.
sage: A = matrix.random(CDF, 500, sparse=True)
sage: I = matrix.identity(CDF, 500, sparse=True)
sage: A = A*A.conjugate_transpose() + I
and then open another terminal and run "sage", you'll get the error. I do that all the time (impatience is a top reason I open multiple sessions), so I think it's very likely that this is a regression.
I don't see anything relevant in https://ipython.readthedocs.io/en/stable/whatsnew/version7.html
I can't reproduce this with 9.5.beta8 on macOS
I wiped my ~/.sage
and the problem persists. It's not a huge deal, everything still works. It's just ugly.
Looks like I'm not the only one, at least: https://github.com/ipython/ipython/issues/12202#issuecomment-990229531
I pretty regularly run multiple sage instances. Today I tried it with 9.5.beta8 for the first time and got,
Then upon exiting,
I don't think we need to display that. Running multiple instances of something (like bash itself) that accesses a single history file has always been caveat emptor.
Component: user interface
Issue created by migration from https://trac.sagemath.org/ticket/33025