<p dir="ltr"><br>
On May 6, 2014 9:47 AM, "Daniel Narvaez" <<a href="mailto:dwnarvaez@gmail.com">dwnarvaez@gmail.com</a>> wrote:<br>
><br>
> On 1 May 2014 14:42, kunal arora <<a href="mailto:kunalarora.135@gmail.com">kunalarora.135@gmail.com</a>> wrote:<br>
>><br>
>> 4)Create a new Sugar-toolkit-gtk3-python3 from the old one and also keep the Sugar-toolkit-gtk3 for activities that haven't yet ported to Python3 and slowly deprecate it with time as more and more activities shift to Python3.<br>
><br>
><br>
> This sounds like a maintenance nightmare. Can we make sugar-toolkit-gtk3 work with both python2 and python3 instead?</p>
<p dir="ltr">Why would we need to maintain a py2 version; we don't maintain the gtk2 toolkit or even care to put it on GitHub.</p>