1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
|
Introduction
============
This is the reference guide for SIP 4.10.5. SIP is a tool for
automatically generating `Python <http://www.python.org>`__ bindings for C and
C++ libraries. SIP was originally developed in 1998 for
`PyTQt <http://www.riverbankcomputing.com/software/pytqt>`__ - the Python
bindings for the TQt GUI toolkit - but is suitable for generating bindings for
any C or C++ library.
This version of SIP generates bindings for Python v2.3 or later, including
Python v3.
There are many other similar tools available. One of the original such tools
is `SWIG <http://www.swig.org>`__ and, in fact, SIP is so called because it
started out as a small SWIG. Unlike SWIG, SIP is specifically designed for
bringing together Python and C/C++ and goes to great lengths to make the
integration as tight as possible.
The homepage for SIP is http://www.riverbankcomputing.com/software/sip. Here
you will always find the latest stable version and the latest version of this
documentation.
SIP can also be downloaded from the
`Mercurial <http://mercurial.selenic.com/>`__ repository at
http://www.riverbankcomputing.com/hg/sip.
License
-------
SIP is licensed under similar terms as Python itself. SIP is also licensed
under the GPL (both v2 and v3). It is your choice as to which license you
use. If you choose the GPL then any bindings you create must be distributed
under the terms of the GPL.
Features
--------
SIP, and the bindings it produces, have the following features:
- bindings are fast to load and minimise memory consumption especially when
only a small sub-set of a large library is being used
- automatic conversion between standard Python and C/C++ data types
- overloading of functions and methods with different argument signatures
- support for Python's keyword argument syntax
- support for both explicitly specified and automatically generated docstrings
- access to a C++ class's protected methods
- the ability to define a Python class that is a sub-class of a C++ class,
including abstract C++ classes
- Python sub-classes can implement the :meth:`__dtor__` method which will be
called from the C++ class's virtual destructor
- support for ordinary C++ functions, class methods, static class methods,
virtual class methods and abstract class methods
- the ability to re-implement C++ virtual and abstract methods in Python
- support for global and class variables
- support for global and class operators
- support for C++ namespaces
- support for C++ templates
- support for C++ exceptions and wrapping them as Python exceptions
- the automatic generation of complementary rich comparison Q_SLOTS
- support for deprecation warnings
- the ability to define mappings between C++ classes and similar Python data
types that are automatically invoked
- the ability to automatically exploit any available run time type information
to ensure that the class of a Python instance object matches the class of the
corresponding C++ instance
- the ability to change the type and meta-type of the Python object used to
wrap a C/C++ data type
- full support of the Python global interpreter lock, including the ability to
specify that a C++ function of method may block, therefore allowing the lock
to be released and other Python threads to run
- support for consolidated modules where the generated wrapper code for a
number of related modules may be included in a single, possibly private,
module
- support for the concept of ownership of a C++ instance (i.e. what part of the
code is responsible for calling the instance's destructor) and how the
ownership may change during the execution of an application
- the ability to generate bindings for a C++ class library that itself is built
on another C++ class library which also has had bindings generated so that
the different bindings integrate and share code properly
- a sophisticated versioning system that allows the full lifetime of a C++
class library, including any platform specific or optional features, to be
described in a single set of specification files
- the ability to include documentation in the specification files which can be
extracted and subsequently processed by external tools
- the ability to include copyright notices and licensing information in the
specification files that is automatically included in all generated source
code
- a build system, written in Python, that you can extend to configure, compile
and install your own bindings without worrying about platform specific issues
- support for building your extensions using distutils
- SIP, and the bindings it produces, runs under UNIX, Linux, Windows and
MacOS/X
SIP Components
--------------
SIP comprises a number of different components.
- The SIP code generator (:program:`sip`). This processes :file:`.sip`
specification files and generates C or C++ bindings. It is covered in detail
in :ref:`ref-using`.
- The SIP header file (:file:`sip.h`). This contains definitions and data
structures needed by the generated C and C++ code.
- The SIP module (:file:`sip.so` or :file:`sip.pyd`). This is a Python
extension module that is imported automatically by SIP generated bindings and
provides them with some common utility functions. See also
:ref:`ref-python-api`.
- The SIP build system (:file:`sipconfig.py`). This is a pure Python module
that is created when SIP is configured and encapsulates all the necessary
information about your system including relevant directory names, compiler
and linker flags, and version numbers. It also includes several Python
classes and functions which help you write configuration scripts for your own
bindings. It is covered in detail in :ref:`ref-build-system`.
- The SIP distutils extension (:file:`sipdistutils.py`). This is a distutils
extension that can be used to build your extension modules using distutils
and is an alternative to writing configuration scripts with the SIP build
system. This can be as simple as adding your .sip files to the list of files
needed to build the extension module. It is covered in detail in
:ref:`ref-distutils`.
TQt Support
-----------
SIP has specific support for the creation of bindings based on Nokia's Qt
toolkit.
The SIP code generator understands the signal/slot type safe callback mechanism
that TQt uses to connect objects together. This allows applications to define
new Python Q_SIGNALS, and allows any Python callable object to be used as a slot.
SIP itself does not require TQt to be installed.
|
