[Sugar-devel] Port to python 3 project

[James Cameron]

Yes, the GSoC project idea is for porting Sugar and the core
activities.

The Toolkit is to be Python 2 and Python 3 according to how it is
installed.  A typical system may have two installs of the Toolkit.

Porting of other activities can be done if there is time available, or
as part of demonstrating your capability in a proposal.

Sugargame is ported, but is waiting for release of Toolkit.

https://github.com/sugarlabs/sugargame/issues/2
https://github.com/sugarlabs/sugargame/pull/5
https://github.com/sugarlabs/sugargame/tree/python3

But don't imagine the GSoC project idea is only porting of source
code; there must also be releasing, packaging, and testing.  It was
too much for GSoC 2018.

On Tue, Mar 12, 2019 at 02:26:34PM +0530, aniket mathur wrote:
> Porting of all fructose activities was included as a part of the GSOC project.
> Does porting other activities to python 3 is not required  or simply  it is of
> less priority?
> Sugargame is also not ported to python 3.

> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel


-- 
James Cameron
http://quozl.netrek.org/