10,579
edits
Changes
Jump to navigation
Jump to search
Line 81:
Line 81: − + Line 89:
Line 89: −
Summer of Code/2014/Proposal to port sugar core to python3 (view source)
Revision as of 12:38, 20 March 2014
, 12:38, 20 March 2014→Me and the community
At the end of my project, the testing on the sugar toolkit and the sugar core would have improved greatly and I strongly believe that a robust set of unit tests is a must for every project as it eases development. Python 3 has better unicode support and I think a lot of activities based around text would greatly benefit from porting to python 3.
At the end of my project, the testing on the sugar toolkit and the sugar core would have improved greatly and I strongly believe that a robust set of unit tests is a must for every project as it eases development. Python 3 has better unicode support and I think a lot of activities based around text would greatly benefit from porting to python 3.
There are several reasons why this project is important to Sugar Labs: (1) we need to keep pace with the projects we depend upon upstream -- Python 3 is being to become de rigour -- and (2) Python 3 has much better support for i18n and unicode -- critical to the global nature of our project. --[[User:Walter|Walter]] ([[User talk:Walter|talk]]) 13:38, 20 March 2014 (EDT)
* How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?
* How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?
I plan to write a report every week on my [http://upman.github.io blog] and also discuss with people regularly over the mailing list or the IRC channel.
I plan to write a report every week on my [http://upman.github.io blog] and also discuss with people regularly over the mailing list or the IRC channel.
===Miscellaneous===
===Miscellaneous===