Re: [Python-Dev] 2.6 and 3.0 tasks

I haven't been around during the 1.x -> 2.x days. I was still in the dark ages (aka PHP user).

:-)

How do you want me to tackle down the PyString / PyBytes problem?

I think it can actually be simplified. I think maintaining binary compatibility between 2.6 and earlier versions is hopeless anyway, so we might as well just rename PyString to PyBytes in 2.6 and 3.0, and have an extra set of macros so that code using PyString needs to be recompiled but not otherwise touched. E.g. typedef { ... } PyBytesObject; #define PyStringObject PyBytesObject ... PyString_Type; #define PyBytes_Type PyString_Type <etc> -- --Guido van Rossum (home page: http://www.python.org/~guido/)