1227
Comment:
|
1646
|
Deletions are marked like this. | Additions are marked like this. |
Line 27: | Line 27: |
=== Journal (status updates - dates in ISO format) === * 2010-06-14: Using 2to3 and some hand-editing, I managed to get "hg version" running in py3k. Need to recheck the generated patch and find a strategy to solve those trouble spots. * 2010-06-15: Attended to GSoC meeting @ #mercurial; submitted some documentation improvements to py3k (http://bugs.python.org/issue9001 & http://bugs.python.org/issue9002). |
Renato Cunha
Contact
Blog: http://valedotrovao.com
Email: <renato AT SPAMFREE renatocunha DOT com>
Homepage: http://renatocunha.com
IRC: trovao @ irc.freenode.net
About me
Currently pursuing a master's degree in Computer Science. Have been working with python for about four years, mostly in hobby projects. Have become a mercurial user at the end of 2009.
I also have some experience with Open Source software development, gained by contributing code and documentation patches to some projects I use and by working on dropline GNOME.
Idea for GSoC 2010
My application's text is located at http://bitbucket.org/trovao/gsoc-2010/src/tip/application.rst.
Implementation status
First of all, my patch queue is located at http://bitbucket.org/trovao/hg-py3k-patches and its corresponding feed is located at http://bitbucket.org/trovao/hg-py3k-patches/rss.
As of 2010-06-08 I've ported the core C modules to python 3. The decisions taken when porting it were based on the idea that hg operates on bytes, and, thus, the new modules operate on and return bytes objects.
Journal (status updates - dates in ISO format)
- 2010-06-14: Using 2to3 and some hand-editing, I managed to get "hg version" running in py3k. Need to recheck the generated patch and find a strategy to solve those trouble spots.
2010-06-15: Attended to GSoC meeting @ #mercurial; submitted some documentation improvements to py3k (http://bugs.python.org/issue9001 & http://bugs.python.org/issue9002).