[Python-Dev] ctypes patch

Thomas Heller theller at python.net
Thu Feb 2 19:55:50 CET 2006

Hye-Shik Chang <hyeshik at gmail.com> writes:

> On 1/30/06, "Martin v. Löwis" <martin at v.loewis.de> wrote:
>> Hye-Shik Chang wrote:
>> > I did some work to make ctypes+libffi compacter and liberal.
>> > http://openlook.org/svnpublic/ctypes-compactffi/  (svn)
>> >
>> > I removed sources/gcc and put sources/libffi copied from gcc 4.0.2.
>> > And removed all automake-related build processes and integrated
>> > them into setup.py. There's still aclocal.m4 in sources/libffi. But
>> > it is just identical to libffi's acinclude.m4 which looks liberal.
>> Well done! Would you like to derive a Python patch from that?
>> Don't worry about MSVC, yet, I will do that once the sources
>> are in the subversion.
> Here goes patches for the integration:
> [1] http://people.freebsd.org/~perky/ctypesinteg-f1.diff.bz2
> [2] http://people.freebsd.org/~perky/ctypesinteg-f2.diff.bz2
> I implemented it in two flavors.  [1] runs libffi's configure along with
> Python's and setup.py just builds it.  And [2] has no change to
> Python's configure and setup.py runs libffi configure and builds it.
> And both patches don't have things for documentations yet.

My plan is to make separate ctypes releases for 2.3 and 2.4, even after
it is integrated into Python 2.5, so it seems [2] would be better - it
must be possible to build ctypes without Python.

As I said before, docs need still to be written.  I think content is
more important than markup, so I'm writing in rest, it can be converted
to latex later.  I expect that writing the docs will show quite some
edges that need to be cleaned up - that should certainly be done before
the first 2.5 release.

Also I want to make a few releases before declaring the 1.0 version.
This does not mean that I'm against integrating it right now.

>> (Of course, for due process, it would be better if this code gets
>> integrated into the official ctypes first, and then we incorporate
>> some named/versioned snapshot into /external, and svn cp it into
>> python/trunk from there).
> Thomas and I collaborated on integration into the ctypes repository
> and testing on various platforms yesterday.  My patches for Python
> are derived from ctypes CVS with a change of only one line.
Hye-Shik has done a great job!  Many thanks to him for that.


More information about the Python-Dev mailing list