<div dir="auto">Sugar logs show in shell.log and activity logs show in activity specific log usually in the form bundle_id.log, your print statements not being shown might mean they were never executed. The other folder it showed in are older logs hence the print statement executed sometime when you tested.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Apr 27, 2021, 8:01 AM Sourabha G <<a href="mailto:sourabha.project@gmail.com" target="_blank" rel="noreferrer">sourabha.project@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><font face="arial, sans-serif">Thanks for the detailed explanation. I tried modifying Sugar and the changes persist. The traceback and errors are shown in the log files, but the debug output<span style="color:rgb(0,0,0)">(print statements)</span> does not show up in log files (But it did show only once in shell.log inside one of the 4 directories labelled with 10 digits numbers). Is there any other files other than shell.log where the output might get stored? </font></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Apr 18, 2021 at 9:00 AM James Cameron <<a href="mailto:quozl@laptop.org" rel="noreferrer noreferrer" target="_blank">quozl@laptop.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">Ibiam has answered you, but I'll just add a bit of context.<br>
<br>
Sugar is a "desktop environment", which means it is a graphical shell<br>
program and a suite of other programs activated from that shell. It<br>
is run (using python module jarabe) as the first and only program of a<br>
graphical login session, e.g. through Xsession.<br>
<br>
Sugar uses GNU conventions for software package building and<br>
installing. We know this as "configure, make, make install". The<br>
method works on pretty much every major Linux distribution.<br>
<br>
Each Linux distribution may follow different conventions for how<br>
programs, or Python programs in particular, are installed.<br>
<br>
Sugar Live Build is built from the Debian distribution, and so most<br>
closely tracks how Debian developers install software.<br>
<br>
However, it does not exactly match.<br>
<br>
The domain specific knowledge needed is operating system software<br>
distribution internals, and specific knowledge about how Python<br>
programs are installed by distribution packages on a Debian system.<br>
<br>
Once you know how a Python program is installed on a system for all<br>
users of that system to use, you have the first step of many.<br>
<br>
On Sat, Apr 17, 2021 at 05:06:29PM +0530, Sourabha G wrote:<br>
> Hi everyone, <br>
> How to test the modified source of sugar from within Sugar DE? I cloned the<br>
> sugar repo but not sure how to test the modification.<br>
> <br>
> Thank you.<br>
<br>
> _______________________________________________<br>
> Sugar-devel mailing list<br>
> <a href="mailto:Sugar-devel@lists.sugarlabs.org" rel="noreferrer noreferrer" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer noreferrer noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
<br>
<br>
-- <br>
James Cameron<br>
<a href="https://quozl.linux.org.au/" rel="noreferrer noreferrer noreferrer" target="_blank">https://quozl.linux.org.au/</a><br>
</blockquote></div>
_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org" rel="noreferrer noreferrer" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer noreferrer noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
</blockquote></div>