David Beazley wrote: > > > > > Misc > > > > Depending on how deep I want to dig, I may have some patches to > ParseTuple() that would make life easier for some of us extension > writing fans. As it is right now, my experimental version of Swig > is using it's own version of ParseTuple (for various reasons). > Also, out of curiousity, is anyone making heavy use of the CObject > type right now? You mean the one in Objects/cobject.c ? Sure, all my type extensions export their C API that way... and it works just great (no more linker problems, nice error messages when extensions are not found, etc.). -- Marc-Andre Lemburg Y2000: 254 days left --------------------------------------------------------------------- : Python Pages >>> http://starship.skyport.net/~lemburg/ : ---------------------------------------------------------
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4