From: SPE Stani’s Python Editor [mailto:spe.stani.be@gmail.com]
…snip…
I’d like to second this. I’ve been trying to use SPE, but I can’t
because SciTE does a much better job at running my scripts from within
i ts environment.
In which sense? That the output is redirected within SciTE? I guess I can figure that out, so that could be implemented in SPE as well.
Exactly. I use that all the time. It’s particularly useful because it provides a history of multiple runs, it’s easy to cut and paste, and it’s searchable.
One other minor nit. I frequently write little test scripts in SciTE. Before execution, I select "File | Save As ..." and simply set the file name to "\temp\temp.py". It appears that in SPE I have to navigate the File Save As dialog to \temp and then save as temp.py to achieve the
same thing.
I guess in this case you are trying to test some code, rather then running a full blown program. In that case SPE doesn’t even require you to save your files (but to be sure will ask you with a dialog box. You can turn off this dialog in the preferences if you know what you are doing.)
Just select the code you want to test and do “Edit>Execute in shell” (Ctrl+Shift+E, if you don’t like this shortcut, change it in whatever you want.). This will execute the code snippet in the shell and give you the feedback for every executed block within that selection. Afterwards you can explore interactively all the variables through the locals browser and the shell. (Does SciTE offer this as well?)
Thanks. I’ll try that. On the other hand, the current behavior is contrary to what I’d expect (not being able to specify the path as part of the filename when saving). I’d like to be able to use it that way even when I’m not just testing scripts.