<div dir="auto">If there's only little advantage for porting to six over porting to py3, why are people still using six?</div> <div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Aug 10, 2020, 5:25 AM James Cameron <<a href="mailto:quozl@laptop.org">quozl@laptop.org</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">No, we're not using it everywhere. It is easier to port to Python 3 than to port using Six, and there's little advantage to having an activity source code compatible with both versions of Python. For new installs of Sugar, or when using Fedora, Debian, or Ubuntu, only Python 3 activities are used. This is because those distributions have chosen for cost reasons to remove support rather than take over security maintenance of Python from the Python Foundation. (Red Hat Enterprise Linux and the other paid enterprise Linux distributions have kept Python 2 available.) For OLPC OS, both Python 2 and Python 3 activities can be used. On Mon, Aug 10, 2020 at 04:42:36AM +0530, Sumit Srivastava wrote: > Awesome! Are we using six everywhere? > > On Mon, Aug 10, 2020, 4:41 AM James Cameron <[1]<a href="mailto:quozl@laptop.org" target="_blank" rel="noreferrer">quozl@laptop.org</a>> wrote: > > Yes, well done, it is very useful. We have used Six on the Sugar > Toolkit so that Python 2 activities can continue to run. > > On Mon, Aug 10, 2020 at 01:10:06AM +0530, Sumit Srivastava wrote: > > Hi all, > > > > I think this might be useful for making activities compatible. I found > this > > while reading the codebase of a software I was using. > > > > [1][2]<a href="https://six.readthedocs.io/" rel="noreferrer noreferrer" target="_blank">https://six.readthedocs.io/</a> > > [2][3]<a href="https://github.com/benjaminp/six" rel="noreferrer noreferrer" target="_blank">https://github.com/benjaminp/six</a> > > > > Regards, > > Sumit > > [t]ᐧ > > > > References: > > > > [1] [4]<a href="https://six.readthedocs.io/" rel="noreferrer noreferrer" target="_blank">https://six.readthedocs.io/</a> > > [2] [5]<a href="https://github.com/benjaminp/six" rel="noreferrer noreferrer" target="_blank">https://github.com/benjaminp/six</a> > > > _______________________________________________ > > Sugar-devel mailing list > > [6]<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank" rel="noreferrer">Sugar-devel@lists.sugarlabs.org</a> > > [7]<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> > > -- > James Cameron > [8]<a href="http://quozl.netrek.org/" rel="noreferrer noreferrer" target="_blank">http://quozl.netrek.org/</a> > > References: > > [1] mailto:<a href="mailto:quozl@laptop.org" target="_blank" rel="noreferrer">quozl@laptop.org</a> > [2] <a href="https://six.readthedocs.io/" rel="noreferrer noreferrer" target="_blank">https://six.readthedocs.io/</a> > [3] <a href="https://github.com/benjaminp/six" rel="noreferrer noreferrer" target="_blank">https://github.com/benjaminp/six</a> > [4] <a href="https://six.readthedocs.io/" rel="noreferrer noreferrer" target="_blank">https://six.readthedocs.io/</a> > [5] <a href="https://github.com/benjaminp/six" rel="noreferrer noreferrer" target="_blank">https://github.com/benjaminp/six</a> > [6] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank" rel="noreferrer">Sugar-devel@lists.sugarlabs.org</a> > [7] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> > [8] <a href="http://quozl.netrek.org/" rel="noreferrer noreferrer" target="_blank">http://quozl.netrek.org/</a> -- James Cameron <a href="http://quozl.netrek.org/" rel="noreferrer noreferrer" target="_blank">http://quozl.netrek.org/</a> </blockquote></div>