Sybren Stuvel wrote:
It runs now, but some things aren't working.
Besides the crashing down, what else? I am very curious.
When I open a file and
click on the browse tab, I see the current directory. If I then
double-click on a Python file, I'd expect SPE to open it, but nothing
happens.
SPE - Stani's Python Editor enlightened us with:
This is a misinterpretation, SPE failed because of something else.
(As would have become clear if you would have run SPE in the
debugging mode 'python SPE.py --debug'.)
IMO displayed messages should be clear without having to resort to a
Sybren Stuvel wrote:
IMO displayed messages should be clear without having to resort to a
debugging mode.
I can agree on that.
Debugging mode should only be for removing bugs, not
for enlightenment of the user.
Unless he doesn't follow the installation instructions.
Anyway, apt-getting spe
SPE - Stani's Python Editor enlightened us with:
If you would have read the blog (http://pythonide.stani.be/blog),
you could clearly read this:
I haven't.
2. download and unpack the archive
SPE-0.8.1.d-wx2.6.1.0-no_setup.zip
If you follow these three steps nothing more, nothing less,