Yes, that is expected. All of our activities that are ported were done so without using Six directly. Only the toolkit was ported using Six, so that the toolkit would continue to be available for both versions of Python during the transition.
On Mon, Aug 10, 2020 at 06:09:21AM +0530, Sumit Srivastava wrote: > 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 <[1][email protected]> 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][2][email protected]> > 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][3] > [email protected]> > > 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][4]https://six.readthedocs.io/ > > > > [2][3][4][5]https://github.com/benjaminp/six > > > > > > > > Regards, > > > > Sumit > > > > [t]ᐧ > > > > > > > > References: > > > > > > > > [1] [4][5][6]https://six.readthedocs.io/ > > > > [2] [5][6][7]https://github.com/benjaminp/six > > > > > > > _______________________________________________ > > > > Sugar-devel mailing list > > > > [6][7][8][email protected] > > > > [7][8][9]http://lists.sugarlabs.org/listinfo/sugar-devel > > > > > > -- > > > James Cameron > > > [8][9][10]http://quozl.netrek.org/ > > > > > > References: > > > > > > [1] mailto:[10][11][email protected] > > > [2] [11][12]https://six.readthedocs.io/ > > > [3] [12][13]https://github.com/benjaminp/six > > > [4] [13][14]https://six.readthedocs.io/ > > > [5] [14][15]https://github.com/benjaminp/six > > > [6] mailto:[15][16][email protected] > > > [7] [16][17]http://lists.sugarlabs.org/listinfo/sugar-devel > > > [8] [17][18]http://quozl.netrek.org/ > > > > -- > > James Cameron > > [18][19]http://quozl.netrek.org/ > > > > References: > > > > [1] mailto:[20][email protected] > > [2] mailto:[21][email protected] > > [3] [22]https://six.readthedocs.io/ > > [4] [23]https://github.com/benjaminp/six > > [5] [24]https://six.readthedocs.io/ > > [6] [25]https://github.com/benjaminp/six > > [7] mailto:[26][email protected] > > [8] [27]http://lists.sugarlabs.org/listinfo/sugar-devel > > [9] [28]http://quozl.netrek.org/ > > [10] mailto:[29][email protected] > > [11] [30]https://six.readthedocs.io/ > > [12] [31]https://github.com/benjaminp/six > > [13] [32]https://six.readthedocs.io/ > > [14] [33]https://github.com/benjaminp/six > > [15] mailto:[34][email protected] > > [16] [35]http://lists.sugarlabs.org/listinfo/sugar-devel > > [17] [36]http://quozl.netrek.org/ > > [18] [37]http://quozl.netrek.org/ > > -- > James Cameron > [38]http://quozl.netrek.org/ > > References: > > [1] mailto:[email protected] > [2] mailto:[email protected] > [3] mailto:[email protected] > [4] https://six.readthedocs.io/ > [5] https://github.com/benjaminp/six > [6] https://six.readthedocs.io/ > [7] https://github.com/benjaminp/six > [8] mailto:[email protected] > [9] http://lists.sugarlabs.org/listinfo/sugar-devel > [10] http://quozl.netrek.org/ > [11] mailto:[email protected] > [12] https://six.readthedocs.io/ > [13] https://github.com/benjaminp/six > [14] https://six.readthedocs.io/ > [15] https://github.com/benjaminp/six > [16] mailto:[email protected] > [17] http://lists.sugarlabs.org/listinfo/sugar-devel > [18] http://quozl.netrek.org/ > [19] http://quozl.netrek.org/ > [20] mailto:[email protected] > [21] mailto:[email protected] > [22] https://six.readthedocs.io/ > [23] https://github.com/benjaminp/six > [24] https://six.readthedocs.io/ > [25] https://github.com/benjaminp/six > [26] mailto:[email protected] > [27] http://lists.sugarlabs.org/listinfo/sugar-devel > [28] http://quozl.netrek.org/ > [29] mailto:[email protected] > [30] https://six.readthedocs.io/ > [31] https://github.com/benjaminp/six > [32] https://six.readthedocs.io/ > [33] https://github.com/benjaminp/six > [34] mailto:[email protected] > [35] http://lists.sugarlabs.org/listinfo/sugar-devel > [36] http://quozl.netrek.org/ > [37] http://quozl.netrek.org/ > [38] http://quozl.netrek.org/ -- James Cameron http://quozl.netrek.org/ _______________________________________________ Sugar-devel mailing list [email protected] http://lists.sugarlabs.org/listinfo/sugar-devel
