. . . . . . . "1053276005"^^ . "Phil Thompson"@en . . . . . . . "SIP (software)"@en . . . . . . . "developer and maintainer"@en . . . "SIP is an open source software tool used to connect computer programs or libraries written in C or C++ with the scripting language Python. It is an alternative to SWIG. SIP was originally developed in 1998 for PyQt \u2014 the Python bindings for the Qt GUI toolkit \u2014 but is suitable for generating bindings for any C or C++ library."@en . . . . . . . . . . . . . . . . "GPL and other"@en . . "32444509"^^ . . . . . . "3268"^^ . "SIP"@en . . "SIP"@en . . . . . "SIP is an open source software tool used to connect computer programs or libraries written in C or C++ with the scripting language Python. It is an alternative to SWIG. SIP was originally developed in 1998 for PyQt \u2014 the Python bindings for the Qt GUI toolkit \u2014 but is suitable for generating bindings for any C or C++ library."@en . . "For PyQt v4 I use an internal tool called . This is sort of an IDE for SIP. It uses GCC-XML to parse the latest header files and saves the relevant data, as XML, in a project. then does the equivalent of a diff against the previous version of the API and flags up any changes that need to be looked at. Those changes are then made through the GUI and ticked off the TODO list. Generating the files is just a button click. In my subversion repository, PyQt v4 is basically just a 20M XML file. Updating PyQt v4 for a minor release of Qt v4 is about half an hours work.\n\nIn terms of how the generated code works then I don't think it's very different from how any other bindings generator works. Python has a very good C API for writing extension modules - it's one of the reasons why so many 3rd party tools have Python bindings. For every C++ class, the SIP generated code creates a corresponding Python class implemented in C."@en . . . . . . . .