Hi Nick and all, I love live coding, and the students enjoy it, too. I often use Spyder and have longer code snippets in the editor window, then press F5 to get the objects that this code defines into the namespace of the prompt, then use the prompt to play around with the defined objects interactively. Or develop small code snippets at the prompt, and when they work, copy them into a python file (either in the Spyder editor, or some other editor).
Ideally, you have the code you edit and the window in which you execute the console visible at the same time. Any ‘switching’ (so that one disappears) makes it very hard for the audience to follow - they want to be able to read and process all the information at their own pace. The Jupyter Notebook is also cool for something like this, but I generally hesitate to use it with complete beginners as it introduces additional complexity. Best wishes, Hans On 5 Nov 2016, at 12:43, nick james <[email protected]<mailto:[email protected]>> wrote: Hi, I've had a quick look through the archive looking for killer objections to the idea of editing a file, say scratch.py, then switching to a console window and doing 'python scratch.py'? This MO doesn't seem to be deprecated or recommended; I'd be interested to hear comments or pointers to discussions I've missed. Nick J _______________________________________________ Discuss mailing list [email protected]<mailto:[email protected]> http://lists.software-carpentry.org/listinfo/discuss Hans Fangohr University of Southampton phone: 023 80598345 email: [email protected]<mailto:[email protected]> www: http://www.soton.ac.uk/~fangohr blog: http://www.soton.ac.uk/~fangohr/blog @ProfCompMod: https://twitter.com/profcompmod _______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/listinfo/discuss
