[Python-Dev] Any PEP about 2.6 -> 3000 code transition?
anthonybaxter at gmail.com
Thu Jul 24 01:50:45 CEST 2008
As a data point, I just presented a tutorial here at OSCON on Python 3
Porting, and had a number of people asking about C API changes. I
punted for my talk (*) because things are still in flux. Plus I only
had 3 hours. I did suggest that if your extension is just glue to a C
library, you should consider using ctypes.
So yes, collecting this information, even if it's just in a wiki page,
would be a good and popular thing.
(*) slides: http://www.interlink.com.au/anthony/tech/talks/OSCON2008/porting3.pdf
On Mon, Jul 21, 2008 at 2:37 PM, Lennart Regebro <regebro at gmail.com> wrote:
> On Mon, Jul 21, 2008 at 20:16, Brett Cannon <brett at python.org> wrote:
>> But waiting until all the betas have gone out totally defeats the
>> purpose of the betas!
> I agree. Writing an actual *guide* can wait, but documenting the
> differences with code examples is a work that can start now, and I
> agree that it would be great if this would start now.
> But writing a guide might not be a good idea until we know what the
> changes are, and if the API is changing quickly now we don't. :-)
> Lennart Regebro: Zope and Plone consulting.
> +33 661 58 14 64
> Python-Dev mailing list
> Python-Dev at python.org
> Unsubscribe: http://mail.python.org/mailman/options/python-dev/anthony%40interlink.com.au
More information about the Python-Dev