On Launch, no matter what version/location I use, I get the following, or similar, error?warning:
17:17:39 unable to put task 8319(/Library/Frameworks/Python.framework/Versions/Current/bin/python) into same group as self
looks like a permissions problem... is it potentially serious?
No, it just attempts to make the editor handling python support process owned by ScrIDE, so that if ScrIDE crashes, it doesn't leave a python process running. So it's more a safeguard in case things go wrong, as opposed to any sort of real problem (and I've no idea why it will work one time, and the next time you run it it won't).
Now, about $PYTHONPATH (the python shell variable):
How do I make ScrIDE look in at it for paths for *.py files?
(or an I missing something really basic.. (I'm used to launching python at the command line, from which $PYTHONPATH, as well as $PYTHONSTARTUP, are "visible", no matter what python is launched.))
The problem is that when you launch python from your favorite shell, it gets all the environment variables the shell does (or whatever else launches it). So if you were to launch ScrIDE from the command line (via the "open" command) you'd get the same env vars as your shell.
Unfortunately, you normally launch it from the Finder, so it only gets the env vars that the Finder knows about (which aren't many). There is an answer, however (though it will require logging out and in to activate). If the file "~/.MacOSX/environment.plist" exists, the various keys in that plist will be set as environment variables for all GUI apps, so you can create/edit that to include your python variables.
Unfortunately, while ScrIDE extensions can access env vars, there currently isn't a way to set them...
thanks for sticking with me on these, Let's hope they help others,
ps l think the console(s) messaging is super!
That's the exact benefit of a webboard like this.
(And yes, I'm quite fond of the console as well - there are some undocumented preferences that turns on great gory details which have been the only way I've been able to debug some of the "rpc" issues to get debugging working).