[soc2008-general] GSOC project ideas, let's push Python 3.0

[Nick Edds]

After Guido's keynote on Python 3000 Friday morning, I find myself very
interested in a project surrounding the translation of Python 2.x to 3.0,
particularly since I spent my last summer working on a somewhat related
problem, albeit with FORTRAN and Ruby. I have a few questions regarding work
on the 2to3 tool as a GSOC project. How can contribution to the 2to3 tool,
specifically work on its completion and acceleration, be made to fit within
the scope of GSOC project? Also, in submitting a proposal for such a
project, what level of specificity do I need to provide in regards to the
particular aspects of the 2to3 tool that I wish to work on?

Thanks,
Nick

On Tue, Mar 4, 2008 at 7:20 PM, Christian Heimes <lists at cheimes.de> wrote:

> Dear fellow Python developers and users!
>
> Most of you probably know that the PSF and the Python core developer
> team have scheduled the release of Python 3.0.0-final for August 2008.
> Python 3.0 is a new and very important mile stone for Python, the
> language. I like to focus as many GSOC projects as possible on Python
> 3.0. It's essential to have a smooth and straight migration path from
> Python 2.x to 3.0. Otherwise Python 3.0 will not be accepted by the
> broad masses.
>
> None of the GSOC projects can target the core of Python 3.0. It'll be in
> beta or release candidate state when GSOC hits the road. But there are
> plenty of other tasks related to Python 3.0. I've made up a list of
> items I could think of.
>
> - Complete and speed up the 2to3 migration tool. It's *very* slow. The
> task is challenging since it requires profiling, C coding with the
> Python API and understanding of the parser.
>
> - Write a GUI frontend for 2to3 and add some features to 2to3 like
> asking the user if a fixer isn't sure how to migrate an ambiguous piece
> of code.
>
> - Port (parts of) Pyrex/Cython to Python 3.0
>
> - Port (parts of) SWIG to Python 3.0
>
> - Port a small but well known and import project with C and Python code
> to Python 3.0. This project shouldn't focus on the migration itself but
> on creating a detailed step by step tutorial how to port C code to
> Python 3.0. The tutorial should explain how to use the new bytes,
> bytearray and buffer API from C and how code must be changed to support
> PyUnicode for text and PyBytes for binary data.
>
> to be continued ...
>
> Christian
> _______________________________________________
> soc2008-general mailing list
> soc2008-general at python.org
> http://mail.python.org/mailman/listinfo/soc2008-general
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/soc2008-general/attachments/20080316/fb9b8951/attachment.htm