<br><br><div><span class="gmail_quote">On 3/16/08, <b class="gmail_sendername">Travis Oliphant</b> <<a href="mailto:oliphant.travis@ieee.org">oliphant.travis@ieee.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Guido van Rossum wrote:<br> > Moving this to a new subject to keep the discussion of tasks and the<br> > discussion of task tracking tools separate.<br> ><br> > On Sun, Mar 16, 2008 at 9:42 AM, Christian Heimes <<a href="mailto:lists@cheimes.de">lists@cheimes.de</a>> wrote:<br>
>> I did a quick brainstorming with me, myself and I. I came up with a list<br> >> of (IMHO) important tasks.<br> >><br> >> * Stabilize the C API of Python 3.0. I like to rename several prefixes<br>
>> to reduce the confusing: PyBytes -> PyByteArray,<br> ><br> > +1 (also +1 to backporting this to 2.6)<br> ><br> >> PyString -> PyBytes ...<br> ><br> > -1. This will make merging code from 2.6 harder, and causes more work<br>
> for porting C extensions.<br> ><br> >> * Backport the new buffer protocol to 2.6. I spoke to Travis yesterday<br> >> and he said he is trying to get it done during the PyCon sprint. Maybe<br> >> somebody can assist him?<br>
><br> > Does he need assistance?<br> <br> <br>I don't really need help with back-porting the protocol. However, I do<br> need help with the struct module changes. This is a standard-library<br> that I'm hoping to get help with.<br>
<br> -Travis</blockquote><div><br>I'm happy to help with this stuff during the sprint.<br><br></div><br></div><br>