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
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 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,
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,
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 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
Awesome! Are we using six everywhere?
On Mon, Aug 10, 2020, 4:41 AM James Cameron 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
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
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.
https://six.readthedocs.io/
https://github.com/benjaminp/six
Regards,
Sumit
ᐧ
___
Sugar-devel mailing list
7 matches
Mail list logo
