Re: [Python-3000] [Python-Dev] 2.6 and 3.0 tasks

2008-03-22 Thread Martin v. Löwis
> I think it can actually be simplified. I think maintaining binary > compatibility between 2.6 and earlier versions is hopeless anyway ABI-wise or API-wise? I would surely hope that the 2.6 API is "mostly" compatible with the 2.5 API. Regards, Martin

Re: [Python-3000] [Python-Dev] 2.6 and 3.0 tasks

2008-03-16 Thread Gregory P. Smith
On 3/16/08, Travis Oliphant <[EMAIL PROTECTED]> wrote: > > Guido van Rossum wrote: > > Moving this to a new subject to keep the discussion of tasks and the > > discussion of task tracking tools separate. > > > > On Sun, Mar 16, 2008 at 9:42 AM, Christian Heimes <[EMAIL PROTECTED]> > wrote: > >> I

Re: [Python-3000] [Python-Dev] 2.6 and 3.0 tasks

2008-03-16 Thread Collin Winter
On Sun, Mar 16, 2008 at 10:17 AM, Christian Heimes <[EMAIL PROTECTED]> wrote: > Collin Winter wrote: > > The biggest win in terms of performance would be to reimplement the > > pattern matching engine used by the fixers.: it by far dominates the > > running time, taking 99+% of the runtime when

Re: [Python-3000] [Python-Dev] 2.6 and 3.0 tasks

2008-03-16 Thread Trent Nelson
> > * Replace Windows API calls with wide versions to support unicode > >for file names, environment etc. > > +1. This should be broken into separate tasks for each API. What are we referring to here? Calling the W versions explicitly and using wchar_t for everything, or using the TCHAR/TEX

Re: [Python-3000] [Python-Dev] 2.6 and 3.0 tasks

2008-03-16 Thread Christian Heimes
Collin Winter wrote: > The biggest win in terms of performance would be to reimplement the > pattern matching engine used by the fixers.: it by far dominates the > running time, taking 99+% of the runtime when I ran 2to3 over Twisted, > for example. The current design is a heavily-recursive system,

Re: [Python-3000] [Python-Dev] 2.6 and 3.0 tasks

2008-03-16 Thread Martin v. Lšwis
>>> * Replace Windows API calls with wide versions to support unicode >>> for file names, environment etc. >> +1. This should be broken into separate tasks for each API. > > What are we referring to here? Calling the W versions explicitly and > using wchar_t for everything, or using the TCHAR/TE

Re: [Python-3000] [Python-Dev] 2.6 and 3.0 tasks

2008-03-16 Thread Benjamin Peterson
On Sun, Mar 16, 2008 at 11:44 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote: > On Sun, Mar 16, 2008 at 11:26 AM, Benjamin Peterson > <[EMAIL PROTECTED]> wrote: > > On Sun, Mar 16, 2008 at 10:23 AM, Guido van Rossum <[EMAIL PROTECTED]> > wrote: > > > > PyString -> PyBytes ... > > > > > > -1. This

Re: [Python-3000] [Python-Dev] 2.6 and 3.0 tasks

2008-03-16 Thread Collin Winter
On Sun, Mar 16, 2008 at 8:23 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote: > On Sun, Mar 16, 2008 at 9:42 AM, Christian Heimes <[EMAIL PROTECTED]> wrote: .. > > and add the fixers to 2to3 > > +1. I think quite a few changes have not had a fixer added. Again, I > think we should maintain a

Re: [Python-3000] [Python-Dev] 2.6 and 3.0 tasks

2008-03-16 Thread Guido van Rossum
On Sun, Mar 16, 2008 at 11:26 AM, Benjamin Peterson <[EMAIL PROTECTED]> wrote: > On Sun, Mar 16, 2008 at 10:23 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote: > > > PyString -> PyBytes ... > > > > -1. This will make merging code from 2.6 harder, and causes more work > > for porting C extensions. >

Re: [Python-3000] [Python-Dev] 2.6 and 3.0 tasks

2008-03-16 Thread Benjamin Peterson
On Sun, Mar 16, 2008 at 10:23 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote: > Moving this to a new subject to keep the discussion of tasks and the > discussion of task tracking tools separate. > > On Sun, Mar 16, 2008 at 9:42 AM, Christian Heimes <[EMAIL PROTECTED]> > wrote: > > I did a quick b