On Thu, Oct 20, 2005 at 02:49:25PM -0700, Daniel Burrows wrote: > After poking through the code a bit, it looks to me like you could get > a lot of the way towards closing this bug by just installing generic.h in > /usr/include under a suitable name (/usr/include/python-apt/wrappers.h?), > documenting which python-apt structures (if any) are *not* available via > this interface, and making the various object types available (so that > third-party code can type-check function parameters and so on). It's been > a while since I wrote a Python extension, though, so I might be missing > something important. http://docs.python.org/extending/extending.html talks about PyCObject, should we use this or should we do something else? I have no experience in in writing the other way around (from Python to C++). -- Julian Andres Klode - Free Software Developer Debian Developer - Contributing Member of SPI Ubuntu Member - Fellow of FSFE Website: http://jak-linux.org/ XMPP: juliank@jabber.org Debian: http://www.debian.org/ SPI: http://www.spi-inc.org/ Ubuntu: http://www.ubuntu.com/ FSFE: http://www.fsfe.org/
Attachment:
signature.asc
Description: Digital signature