<br><br>On Sun, Jul 17, 2016 at 3:55 AM, Sebastian Silva <email@example.com> wrote:<br>
<blockquote type="cite"><div class="plaintext" style="white-space: pre-wrap;">
El 29/06/16 a las 14:03, Dave Crossland escribió:
<blockquote> On 29 June 2016 at 14:22, Sebastian Silva <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:
<blockquote> Really Sugar Labs doesn't distribute operating system releases, it's up to
</blockquote> If 0.112 is 100% Python 3, how would OLPC or others make images that
support running python2 and python3 activities in the same Sugar?
</blockquote>It's hard to keep up with you but I'll try ;-)
By default distributions will decide which python to use.
If an activity is ported they can change the activity.info to use
python3. Really it shouldn't be a problem.
Note that python2.7 is supposed to have support till 2020.
Python3 is a much nicer language especially if you use non-english
characters since it fully supports utf-8 by default.
The real issue is what to do about telepathy. I wonder how many use
cases are covered by it.</div></blockquote><div><br></div><div>Well, the way that we use telepathy in sugar makes me cringe inside. It is really the most terrible and verbose api for our use case. All of the telepathy code is like black magic. I spent a few hours trying to figure out how to fix , and I got close to nowhere. The telepathy code is very hard to understand. It's actually like an onion. Every layer you peel back makes you cry more, and we just keep layering and layering the abstractions on (eg. CollabWrapper).</div><div><br></div><div>I've been working with Abhijit on his GSoC project to use telepathy for collaboration for the "projects" in the journal. Just creating a text channel to communicate via has been impossible so far. Abhijit has spend weeks trying to do it, and i have attempted to hack it too. But telepathy is very hard to debug. And it is really buggy - creating a text channel between 2 people results in a segfault in telepathy salut, despite what seems to be 100% correct usage of the api. It's crazy.</div><div><br></div><div>But from a porting perspective, telepathy is fine. Python telepathy is made up of 2 things: a tone of string constants (easy to port) and a few wrapper classes that are subclasses of the "dbus" objects. It is pure python - so it should be an easy thing to port.</div><div><br></div><div>So I am sorry for constantly conflating these 2 things. Telepathy is a pain to develop with, BUT it will be easy to port to python 3.</div><div><br></div><div>Maybe we target a collaboration re-write for next release :P</div><div><br></div><div>Thanks,</div><div>Sam</div><br><blockquote type="cite"><div class="plaintext" style="white-space: pre-wrap;">
Sugar-devel mailing list