3 ms·
IPython has a sqlite-backed history too. I manage to corrupt it frequently, presumably due to segfaults in extensions I'm developing, or because I rarely have
by klyrs 5y ago
IPython has a sqlite-backed history too. I manage to corrupt it frequently, presumably due to segfaults in extensions I'm developing, or because I rarely have fewer than 10 sessions open. I don't mind occasionally restarting IPython and very rarely nuking its history... but if that happened to me in bash, I'd be beyond frustrated. Is a non-concurrent database really a good idea here?
- ElectricalUnion 5y ago> non-concurrent database What does this even mean? Is this IPython backed history using Write-Ahead Logging? > I manage to corrupt it frequently, presumably due to segfaults in extensions A C-based program can't defend itself against corrupted memory. Your logger would need to run in a separated process from your actual code. https://www.sqlite.org/howtocorrupt.html#_memory_corruption https://www.sqlite.org/howtocorrupt.html#_memory_corruption