A while ago I switched from Enthought\'s old EPD to their newer Canopy system. For the most part it\'s nice, but one aspect has been particularly vexing.
Whenever
No, this is not a change between EPD and Canopy. While I suppose there might be some python distributions which default to buffering off, EPD was not one of them -- the performance hit could have been too severe (as kindall's comment mentions.) Better to let the programmer decide when it's important for the user to see console output immediately (typically for status updates).
BTW, IPython in the Canopy GUI is simply IPython QtConsole. If you are depending on console I/O, you may also need to be aware of this longstanding issue with QtConsole:
I don't think there's a reasonable workaround for Canopy IPython, other than do it "properly", i.e. with flush.
https://support.enthought.com/entries/22157050-Canopy-Python-prompt-QtConsole-Can-t-run-interactive-OS-shell-commands
This looks like buffered output. Try running your script as:
python -u yourscript
The -u
flag turns buffering off.
(Replace python
by your OS's python executable's name.)