[Sugar-devel] [GSoC] Porting To Python3

Gonzalo Odiard godiard at sugarlabs.org
Tue May 6 08:13:48 EDT 2014


These links can be useful:

https://docs.python.org/3/howto/pyporting.html

http://stackoverflow.com/questions/11372190/python-2-and-python-3-dual-development

https://pythonhosted.org/six/

Gonzalo


On Tue, May 6, 2014 at 8:50 AM, kunal arora <kunalarora.135 at gmail.com>wrote:

>
> The amount of work needed for either strategy will be almost the same but
> in my opinion a codebase compatible with both python2 and python3 will
> actually be harder to maintain as whenever we change something in the core
> or toolkit we'll have to write polyglot code compatible with both python2
> AND python3 . Whereas if go with complete port into a new toolkit we will
> just have to accomodate ourselves in writing code in python3.
> But if you guys think maintaining another toolkit will be harder, then we
> can port sugar core and toolkit to python2 and python3 compatible code and
> follow the strategy mentioned above by Gonzalo.
>
> Kunal
>



-- 
Gonzalo Odiard

SugarLabs - Software for children learning
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20140506/2c8e5d80/attachment.html>


More information about the Sugar-devel mailing list