24 comments:

I tried installing the package and the install went fine. When trying to run SPE I got an error that /Library/Frameworks/Python.framework/ Versions/2.5/Resources/Python.app/ Contents/MacOS/Python could not be found. (spaces in path added to make the blogger show the entire line)

I changed the #! at the top of /Applications/SPE/Contents/MacOS/SPE to

/Applications/SPE/Contents/MacOS/Python

and all worked fine.

I am not sure if this change was needed because of a package I am missing or what.

I've just installed this version. It really looks good, but I have an annoying problem: If I write e.g. math. a call tip appears (well, that's not the problem) and after if disappears my keyboard is dead inside the editor window.

I successfully dragged the program to the application folder BUT when I tried to launch it, the icon kept bouncing in the dock and then disappeared. I tried different times the same operation but got the same result.

Hi, Stani. As with others I had to change the #! to make the package run. I believe that Krzysztof's use of a specific path (#!/Library/Frameworks/Python.framework/Versions/2.5/Resources/Python.app/Contents/MacOS/Python) is not ideal, as it relies on a specific configuration; it might be safer to have #!/usr/bin/env python instead.

I am sending this comment to Krzysztof as well.

If I understand what is supposed to happen I believe there is another glitch in SPE. When I try to "Run Without Argument" the run fails apparently because there is a space in the file path. The file is /Users/iayork/Scripts/XPlasMap/XPlasMap v.1.0/XPlasMap.py and the error message says/Users/iayork/Downloads/SPE.app/Contents/MacOS/Python: '/Users/iayork/Scripts/XPlasMap/XPlasMap' is a directory, cannot continue

So it seems to be truncating the path at the space.

I've been following SPE with interest since shortly after you first introduced it and hope these glitches can get sorted out, because I'd like to start using it as my main IDE.

Hey -- If anyone else has the problem where you've installed the app, but it won't run, try to alter the shebang, as described above (ctrl-click SPE in the applications folder, open Contents, MacOS, then open SPE with textedit or some other editor, change the first line to #!/usr/bin/env python )

Once you've done that, if it still doesn't load,try opening that same file with terminal (Applications -> utilities-> terminal) and it may give you a message that wxPython is not installed (it did for me) proceed to www.wxpython.org and grab whichever flavor best suits you, then try re-launching SPE. Worked for me, hopefully it can help someone else too.

Buba with spe and wx.In Ubuntu only, in windows work well.Wrong wx version? I do not have time to check out, but if i try 'run/stop' it seems that wx(2.8) have change since 2.6 and gest hung up.I think that is a easy way to fix, gest switch the call to correct wx element, and I think that SPE should be in the same boat with ubuntu's wx version.

Just installed the dmg. Upon opening SPE, it immediately crashes. I see the following error in my Console log: com.apple.launchd[177] ([0x0-0x249249].SPE[22169]) posix_spawnp("/Applications/SPE.app/Contents/MacOS/SPE", ...): No such file or directory

I doubt that Snow Leopard has anything to do with it.... All the difficulties installing seem to have to do with where you keep Python.

Python installations do not seem to be as standard on the Mac and it may have moved between OS versions. (For instance if Snow Leopard runs 2.6 by default, the path will be different. But it would also be different for folks who have upgraded...)

Do 'which python' in a terminal, to find out where you have it, and change the #! at the start of he file as instructed above.

One thing that is not so great on a Mac, which I guess will also be annoying on Linux: you open non-python files with 'os.startfile', which only exists in Windows. (I don't know why this method is not implemented in Linux or MacOS, it doesn't seem hard, but it is missing).

So if you have a mixed-use project (Python, SQL, HTML, JavaScript...) the user needs to remember to use the Finder to open some files and SPE to open others.

Converting this to use the subprocess module calls would make it platform independent (though perhaps more verbose).

Superb application, works great.Just want to note though that I still had the "bouncing and not launching' issue and had to change the #!... to #!/urs/bin/env python as mentionned above even today (4 years later...:P)