[maemo-developers] Python Launcher released

[From: luciano.wolf at indt.org.br]

It's a bit strange because it uses "which" to discover the real path. Did 
you put your script in a visible path (e.g.: /usr/bin) with execution flag
(chmod +x)? If you run "which myapplication.py" it returns a valid path?

By now the daemon only supports shutdown (python-launcher-daemon -s). This 
stops the daemon but keeps running processes alive. The only way to kill 
the last application is "ps -aux | grep python" and "kill -9 PID" where 
PID is the last started python-daemon-launcher process. But would be better 
to use this only if your app freezes.

Thanks for your reports and interest!


-----Original Message-----
From: maemo-developers-bounces at maemo.org on behalf of ext Jeffrey Barish
Sent: Mon 31-Mar-08 12:04
To: maemo-developers at maemo.org
Subject: Re: Python Launcher released
 
Luciano Miguel Wolf wrote:

> Pylauncher shows this message when wasn't possible to find the script to
> be executed. Try to use "python ./myapplication.py" or the full path to
> the script.
> 
> Regards,
> Luciano Wolf

Yes, prefixing ./ does the trick.  Seems a little strange, though, that
Pylauncher doesn't find a script in the cwd.

One other question: Is there a way to kill myapplication.py once it starts
running under Pylauncher?  I used to use ^c, but Pylauncher exits once it
gets myapplication running.  Can I send a signal to the daemon
(kill -something)?

Start up is definitely faster -- by about 2 seconds.  Nice work.
-- 
Jeffrey Barish

_______________________________________________
maemo-developers mailing list
maemo-developers at maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.maemo.org/pipermail/maemo-developers/attachments/20080331/3e3bcb71/attachment.htm