Open nicokoch opened 9 years ago
This seems like an artifact of us using BufferedProcess instead of the node centric process spawning.
It's something we're running into a lot with numpy/matplotlib scripts since they block execution at a plt.show() command, and traditionally plt.show() is the last line of our scripts.
oooooh, how are you outputting the plots? Just pylab.show()
?
I'm currently working on an electron (nee Atom shell) app to make sidecar output for Jupyter/IPython:
Once that's in a ready state I'll work on proper Atom integration with a full session. Just an experiment for the moment.
I've been trying to get people onto more vanilla python setups in the office to make it easier to share analysis scripts, so it's just matplotlib.pyplot.show() currently.
I just realized that the image I posted above was before I was displaying plots. Silly me.
@superlou there's now an Atom package called Hydrogen that people can use: https://github.com/willwhitney/hydrogen (happily contributing there). I'll certainly be contributing to it.
Came here to report exactly this. Has there been any progress with this issue? Cheers
FYI, script-runner handles this correctly.
Awesome! How does it accept input?
@rgbkrk apparently it doesn't :(
It only handles correctly the printing of executed commands on the go.
The bottom console, which shows the program output will only update itself AFTER the program has terminated. Instead, it would be better if it showed the new output whenever the program outputs something.
This has been tested with the following python script:
After 5 seconds, the bottom console will output
Instead, the 'start' should be printed immediately.