Jay,
did you get those errors with the new script????? checking of python and the modules needed is done by the bash script and missing modules are reported by xmessage.
with the previous version the check was not done properly resulting in python 2.7 starting without the needed modules. The error message you got was from python.
but as I said already this should be fixed with the new script.
Gerrit.
On 29 aug 2011, at 12:27, Jay Moran wrote:
On Mon, Aug 29, 2011 at 6:02 AM, Gerrit Polder pa3bya@amsat.org wrote: the script didn't work properly when both Dan's python and macports python (partially) are installed. I changed it now such that Dan's python is preferred, when that is not installed it checks for the macports version and its installed components.
Please find enclosed the fixed script.
Cool. So, remove the KK7DS py25 stuff... then remove py27-serial to test the one, then py27-gtk to test to make sure the message is thrown it sounds like.
ERRMESG is not a command, just a variable.
Ahhh, that's what I get for not paying more attention.
It was a different type of message box with a octagon stop sign that said ERROR or STOP in it when py27-serial wasn't installed, very different han the smallish black and white message box for the other messages -- like the "failed to run" message I ALSO got after the stop sign message.
No message at all for py27-gtk not being installed and just the "failed to run" message in the smallish box. Must be the way xmessage is called then? Or observer error on my part? Probably need to test with py27-gtk missing and macports py2.7 preferred though just to make sure.
Jay