ScriptPup
commented
4 years ago Correction to this, a little... After using a little more extensively, it looks like each cell isn't just outputting but RUNNING the previous command. This is kind of conjecture, as it's based on seeing variable setting taking around the amount of time I would have taken the previous command to run, and the previous command (which should have taken a bit) running in 0 seconds.
I'm running windows 10 on a fresh install of Jupyter and jupyter-powershell (this is awesome, by the way, 100+ props!) and I've found that cells consistently return their last result as soon as I run them and do not re-run when called. This includes the initial run of a cell returning what looks like a single empty line. (Short video showing the behavior on imgur here).
This is mostly just an annoyance and doesn't really have a huge impact since I can just re-run a cell. The biggest issue is that long-running processes which fail may not show an error until I re-run it, which is how I originally found the issue... I thought my script was running fine but failing to produce anything :)
Let me know if you need any additional information or if there's something I can check on my side. I don't really know anything about kernels or how this is all setup, but if I get a chance before you to investigate I'll let you know what I find - wanted to get this out here since I don't know when that'll be though.