But isn't that already possible by porting? Someone can port to py3 and maintain only that.
On Mon, Aug 10, 2020, 5:49 AM James Cameron <qu...@laptop.org> wrote: > So that they can continue to maintain one source code that will > run on either Python 2 or Python 3. > > On Mon, Aug 10, 2020 at 05:33:47AM +0530, Sumit Srivastava wrote: > > If there's only little advantage for porting to six over porting to py3, > why > > are people still using six? > > > > On Mon, Aug 10, 2020, 5:25 AM James Cameron <[1]qu...@laptop.org> wrote: > > > > 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][2] > qu...@laptop.org> > > 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][3]https://six.readthedocs.io/ > > > > [2][3][4]https://github.com/benjaminp/six > > > > > > > > Regards, > > > > Sumit > > > > [t]ᐧ > > > > > > > > References: > > > > > > > > [1] [4][5]https://six.readthedocs.io/ > > > > [2] [5][6]https://github.com/benjaminp/six > > > > > > > _______________________________________________ > > > > Sugar-devel mailing list > > > > [6][7]Sugar-devel@lists.sugarlabs.org > > > > [7][8]http://lists.sugarlabs.org/listinfo/sugar-devel > > > > > > -- > > > James Cameron > > > [8][9]http://quozl.netrek.org/ > > > > > > References: > > > > > > [1] mailto:[10]qu...@laptop.org > > > [2] [11]https://six.readthedocs.io/ > > > [3] [12]https://github.com/benjaminp/six > > > [4] [13]https://six.readthedocs.io/ > > > [5] [14]https://github.com/benjaminp/six > > > [6] mailto:[15]Sugar-devel@lists.sugarlabs.org > > > [7] [16]http://lists.sugarlabs.org/listinfo/sugar-devel > > > [8] [17]http://quozl.netrek.org/ > > > > -- > > James Cameron > > [18]http://quozl.netrek.org/ > > > > References: > > > > [1] mailto:qu...@laptop.org > > [2] mailto:qu...@laptop.org > > [3] https://six.readthedocs.io/ > > [4] https://github.com/benjaminp/six > > [5] https://six.readthedocs.io/ > > [6] https://github.com/benjaminp/six > > [7] mailto:Sugar-devel@lists.sugarlabs.org > > [8] http://lists.sugarlabs.org/listinfo/sugar-devel > > [9] http://quozl.netrek.org/ > > [10] mailto:qu...@laptop.org > > [11] https://six.readthedocs.io/ > > [12] https://github.com/benjaminp/six > > [13] https://six.readthedocs.io/ > > [14] https://github.com/benjaminp/six > > [15] mailto:Sugar-devel@lists.sugarlabs.org > > [16] http://lists.sugarlabs.org/listinfo/sugar-devel > > [17] http://quozl.netrek.org/ > > [18] http://quozl.netrek.org/ > > -- > James Cameron > http://quozl.netrek.org/ >
_______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel