I thought someone was working on a quick, smooth confirmation path through the Journal.<div><br><br><div class="gmail_quote">On Sun, Feb 22, 2009 at 1:29 PM, Luke Faraone <span dir="ltr"><luke@faraone.cc></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">On Sun, Feb 22, 2009 at 1:16 PM, <<a href="mailto:pgf@laptop.org">pgf@laptop.org</a>> wrote:<br>
> > Ignoring that, you would think you could run one activity from another<br>
> > using a) Python code, b) exec(), or c) DBus.<br>
<br>
exec() is the spawn of satan: all code exec'd is run in your local<br>
namespace and takes over the current thread.<br>
<br>
You can also use os.fork() or the subprocess module to call<br>
sugar-launch-activity, but you'll get perm problems.<br>
<font color="#888888"><br>
--<br>
Luke Faraone<br>
<a href="http://luke.faraone.cc" target="_blank">http://luke.faraone.cc</a><br>
_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
</font></blockquote></div><br></div>