call for help: C-API 2 to 3 porting guide
Hi guys, I remember a while back we were bemoaning the fact that little documentation exists for the extension module transition between 2.x and 3.x. In the name of this effort, I've created a c porting howto (Doc/howto/cporting.rst). I have started a few sections, but I can't do it all alone. Please consider writing a section. -- Cheers, Benjamin Peterson "There's no place like 127.0.0.1."
Benjamin Peterson wrote:
Hi guys, I remember a while back we were bemoaning the fact that little documentation exists for the extension module transition between 2.x and 3.x. In the name of this effort, I've created a c porting howto (Doc/howto/cporting.rst). I have started a few sections, but I can't do it all alone. Please consider writing a section.
I'll try to find some time over the weekend to assist you. I'm going to contact the Cython developers, too. They have a great deal of experience with Python 2.x and 3.0 compatible C code. Perhaps they can give us some hints and tell us about gotchas and tricks. Christian
On Sat, Sep 27, 2008 at 9:09 PM, Christian Heimes
Benjamin Peterson wrote:
Hi guys, I remember a while back we were bemoaning the fact that little documentation exists for the extension module transition between 2.x and 3.x. In the name of this effort, I've created a c porting howto (Doc/howto/cporting.rst). I have started a few sections, but I can't do it all alone. Please consider writing a section.
I'll try to find some time over the weekend to assist you. I'm going to contact the Cython developers, too. They have a great deal of experience with Python 2.x and 3.0 compatible C code. Perhaps they can give us some hints and tell us about gotchas and tricks.
Also, there's a wiki page for some py3k extension moduls migration tips: http://wiki.python.org/moin/Py3kExtensionModules Hope it helps. -- Haoyu Bai
participants (3)
-
Benjamin Peterson -
Christian Heimes -
Haoyu Bai