Using C++ in Cython
Overview
Cython has native support for most of the C++ language. Specifically:
- C++ objects can be dynamically allocated with
new
anddel
keywords. - C++ objects can be stack-allocated.
- C++ classes can be declared with the new keyword
cppclass
. - Templated classes and functions are supported.
- Overloaded functions are supported.
- Overloading of C++ operators (such as operator+, operator[],…) is supported.
Procedure Overview
The general procedure for wrapping a C++ file can now be described as follows:
- Specify C++ language in a
setup.py
script or locally in a source file. - Create one or more
.pxd
files withcdef extern from
blocks and(if existing) the C++ namespace name. In these blocks:- declare classes as
cdef cppclass
blocks - declare public names (variables, methods and constructors)
- declare classes as
cimport
them in one or more extension modules (.pyx
files).
A simple Tutorial
An example C++ API
Here is a tiny C++ API which we will use as an example throughout thisdocument. Let’s assume it will be in a header file calledRectangle.h
:
- #ifndef RECTANGLE_H
- #define RECTANGLE_H
- namespace shapes {
- class Rectangle {
- public:
- int x0, y0, x1, y1;
- Rectangle();
- Rectangle(int x0, int y0, int x1, int y1);
- ~Rectangle();
- int getArea();
- void getSize(int* width, int* height);
- void move(int dx, int dy);
- };
- }
- #endif
and the implementation in the file called Rectangle.cpp
:
- #include <iostream>
- #include "Rectangle.h"
- namespace shapes {
- // Default constructor
- Rectangle::Rectangle () {}
- // Overloaded constructor
- Rectangle::Rectangle (int x0, int y0, int x1, int y1) {
- this->x0 = x0;
- this->y0 = y0;
- this->x1 = x1;
- this->y1 = y1;
- }
- // Destructor
- Rectangle::~Rectangle () {}
- // Return the area of the rectangle
- int Rectangle::getArea () {
- return (this->x1 - this->x0) * (this->y1 - this->y0);
- }
- // Get the size of the rectangle.
- // Put the size in the pointer args
- void Rectangle::getSize (int *width, int *height) {
- (*width) = x1 - x0;
- (*height) = y1 - y0;
- }
- // Move the rectangle by dx dy
- void Rectangle::move (int dx, int dy) {
- this->x0 += dx;
- this->y0 += dy;
- this->x1 += dx;
- this->y1 += dy;
- }
- }
This is pretty dumb, but should suffice to demonstrate the steps involved.
Declaring a C++ class interface
The procedure for wrapping a C++ class is quite similar to that for wrappingnormal C structs, with a couple of additions. Let’s start here by creating thebasic cdef extern from
block:
- cdef extern from "Rectangle.h" namespace "shapes":
This will make the C++ class def for Rectangle available. Note the namespace declaration.Namespaces are simply used to make the fully qualified name of the object,and can be nested (e.g. "outer::inner"
) or even refer toclasses (e.g. "namespace::MyClass
to declare static members on MyClass).
Declare class with cdef cppclass
Now, let’s add the Rectangle class to this extern from block - just copy theclass name from Rectangle.h and adjust for Cython syntax, so now it becomes:
- cdef extern from "Rectangle.h" namespace "shapes":
- cdef cppclass Rectangle:
Add public attributes
We now need to declare the attributes and methods for use on Cython. We put those declarationsin a file called Rectangle.pxd
. You can see it as a header filewhich is readable by Cython:
- cdef extern from "Rectangle.cpp":
- pass
- # Declare the class with cdef
- cdef extern from "Rectangle.h" namespace "shapes":
- cdef cppclass Rectangle:
- Rectangle() except +
- Rectangle(int, int, int, int) except +
- int x0, y0, x1, y1
- int getArea()
- void getSize(int* width, int* height)
- void move(int, int)
Note that the constructor is declared as “except +”. If the C++ code orthe initial memory allocation raises an exception due to a failure, thiswill let Cython safely raise an appropriate Python exception instead(see below). Without this declaration, C++ exceptions originating fromthe constructor will not be handled by Cython.
We use the lines:
- cdef extern from "Rectangle.cpp":
- pass
to include the C++ code from Rectangle.cpp
. It is also possible to specify tosetuptools that Rectangle.cpp
is a source. To do that, you can add this directive at thetop of the .pyx
(not .pxd
) file:
- # distutils: sources = Rectangle.cpp
Note that when you use cdef extern from
, the path that you specify is relative to the currentfile, but if you use the distutils directive, the path is relative to thesetup.py
. If you want to discover the path of the sources whenrunning the setup.py
, you can use the aliases
argumentof the cythonize()
function.
Declare a var with the wrapped C++ class
We’ll create a .pyx
file named rect.pyx
to build our wrapper. We’reusing a name other than Rectangle
, but if you prefer giving the same nameto the wrapper as the C++ class, see the section onresolving naming conflicts.
Within, we use cdef to declare a var of the class with the C++ new
statement:
- # distutils: language = c++
- from Rectangle cimport Rectangle
- def main():
- rec_ptr = new Rectangle(1, 2, 3, 4) # Instantiate a Rectangle object on the heap
- try:
- rec_area = rec_ptr.getArea()
- finally:
- del rec_ptr # delete heap allocated object
- cdef Rectangle rec_stack # Instantiate a Rectangle object on the stack
The line:
- # distutils: language = c++
is to indicate to Cython that this .pyx
file has to be compiled to C++.
It’s also possible to declare a stack allocated object, as long as it hasa “default” constructor:
- cdef extern from "Foo.h":
- cdef cppclass Foo:
- Foo()
- def func():
- cdef Foo foo
- ...
Note that, like C++, if the class has only one constructor and itis a nullary one, it’s not necessary to declare it.
Create Cython wrapper class
At this point, we have exposed into our pyx file’s namespace the interfaceof the C++ Rectangle type. Now, we need to make this accessible fromexternal Python code (which is our whole point).
Common programming practice is to create a Cython extension type whichholds a C++ instance as an attribute and create a bunch offorwarding methods. So we can implement the Python extension type as:
- # distutils: language = c++
- from Rectangle cimport Rectangle
- # Create a Cython extension type which holds a C++ instance
- # as an attribute and create a bunch of forwarding methods
- # Python extension type.
- cdef class PyRectangle:
- cdef Rectangle c_rect # Hold a C++ instance which we're wrapping
- def __cinit__(self, int x0, int y0, int x1, int y1):
- self.c_rect = Rectangle(x0, y0, x1, y1)
- def get_area(self):
- return self.c_rect.getArea()
- def get_size(self):
- cdef int width, height
- self.c_rect.getSize(&width, &height)
- return width, height
- def move(self, dx, dy):
- self.c_rect.move(dx, dy)
And there we have it. From a Python perspective, this extension type will lookand feel just like a natively defined Rectangle class.It should be noted that if you want to giveattribute access, you could just implement some properties:
- # distutils: language = c++
- from Rectangle cimport Rectangle
- cdef class PyRectangle:
- cdef Rectangle c_rect
- def __cinit__(self, int x0, int y0, int x1, int y1):
- self.c_rect = Rectangle(x0, y0, x1, y1)
- def get_area(self):
- return self.c_rect.getArea()
- def get_size(self):
- cdef int width, height
- self.c_rect.getSize(&width, &height)
- return width, height
- def move(self, dx, dy):
- self.c_rect.move(dx, dy)
- # Attribute access
- @property
- def x0(self):
- return self.c_rect.x0
- @x0.setter
- def x0(self, x0):
- self.c_rect.x0 = x0
- # Attribute access
- @property
- def x1(self):
- return self.c_rect.x1
- @x1.setter
- def x1(self, x1):
- self.c_rect.x1 = x1
- # Attribute access
- @property
- def y0(self):
- return self.c_rect.y0
- @y0.setter
- def y0(self, y0):
- self.c_rect.y0 = y0
- # Attribute access
- @property
- def y1(self):
- return self.c_rect.y1
- @y1.setter
- def y1(self, y1):
- self.c_rect.y1 = y1
Cython initializes C++ class attributes of a cdef class using the nullary constructor.If the class you’re wrapping does not have a nullary constructor, you must store a pointerto the wrapped class and manually allocate and deallocate it.A convenient and safe place to do so is in the cinit and dealloc methodswhich are guaranteed to be called exactly once upon creation and deletion of the Pythoninstance.
- # distutils: language = c++
- from Rectangle cimport Rectangle
- cdef class PyRectangle:
- cdef Rectangle*c_rect # hold a pointer to the C++ instance which we're wrapping
- def __cinit__(self, int x0, int y0, int x1, int y1):
- self.c_rect = new Rectangle(x0, y0, x1, y1)
- def __dealloc__(self):
- del self.c_rect
Compilation and Importing
To compile a Cython module, it is necessary to have a setup.py
file:
- from setuptools import setup
- from Cython.Build import cythonize
- setup(ext_modules=cythonize("rect.pyx"))
Run $ python setup.py build_ext —inplace
To test it, open the Python interpreter:
- >>> import rect
- >>> x0, y0, x1, y1 = 1, 2, 3, 4
- >>> rect_obj = rect.PyRectangle(x0, y0, x1, y1)
- >>> print(dir(rect_obj))
- ['__class__', '__delattr__', '__dir__', '__doc__', '__eq__', '__format__', '__ge__',
- '__getattribute__', '__gt__', '__hash__', '__init__', '__init_subclass__', '__le__',
- '__lt__', '__ne__', '__new__', '__reduce__', '__reduce_ex__', '__repr__', '__setattr__',
- '__setstate__', '__sizeof__', '__str__', '__subclasshook__', 'get_area', 'get_size', 'move']
Advanced C++ features
We describe here all the C++ features that were not discussed in the above tutorial.
Overloading
Overloading is very simple. Just declare the method with different parametersand use any of them:
- cdef extern from "Foo.h":
- cdef cppclass Foo:
- Foo(int)
- Foo(bool)
- Foo(int, bool)
- Foo(int, int)
Overloading operators
Cython uses C++ naming for overloading operators:
- cdef extern from "foo.h":
- cdef cppclass Foo:
- Foo()
- Foo operator+(Foo)
- Foo operator-(Foo)
- int operator*(Foo)
- int operator/(int)
- int operator*(int, Foo) # allows 1*Foo()
- # nonmember operators can also be specified outside the class
- double operator/(double, Foo)
- cdef Foo foo = new Foo()
- foo2 = foo + foo
- foo2 = foo - foo
- x = foo * foo2
- x = foo / 1
- x = foo[0] * foo2
- x = foo[0] / 1
- x = 1*foo[0]
- cdef double y
- y = 2.0/foo[0]
Note that if one has pointers to C++ objects, dereferencing must be doneto avoid doing pointer arithmetic rather than arithmetic on the objectsthemselves:
- cdef Foo* foo_ptr = new Foo()
- foo = foo_ptr[0] + foo_ptr[0]
- x = foo_ptr[0] / 2
- del foo_ptr
Nested class declarations
C++ allows nested class declaration. Class declarations can also benested in Cython:
- # distutils: language = c++
- cdef extern from "<vector>" namespace "std":
- cdef cppclass vector[T]:
- cppclass iterator:
- T operator*()
- iterator operator++()
- bint operator==(iterator)
- bint operator!=(iterator)
- vector()
- void push_back(T&)
- T& operator[](int)
- T& at(int)
- iterator begin()
- iterator end()
- cdef vector[int].iterator iter #iter is declared as being of type vector<int>::iterator
Note that the nested class is declared with a cppclass
but without a cdef
,as it is already part of a cdef
declaration section.
C++ operators not compatible with Python syntax
Cython tries to keep its syntax as close as possible to standard Python.Because of this, certain C++ operators, like the preincrement ++foo
or the dereferencing operator *foo
cannot be used with the samesyntax as C++. Cython provides functions replacing these operators ina special module cython.operator
. The functions provided are:
cython.operator.dereference
for dereferencing.dereference(foo)
will produce the C++ code*(foo)
cython.operator.preincrement
for pre-incrementation.preincrement(foo)
will produce the C++ code++(foo)
.Similarly forpredecrement
,postincrement
andpostdecrement
.cython.operator.comma
for the comma operator.comma(a, b)
will produce the C++ code((a), (b))
.
These functions need to be cimported. Of course, one can use afrom … cimport … as
to have shorter and more readable functions.For example: from cython.operator cimport dereference as deref
.
For completeness, it’s also worth mentioning cython.operator.address
which can also be written &foo
.
Templates
Cython uses a bracket syntax for templating. A simple example for wrapping C++ vector:
- # distutils: language = c++
- # import dereference and increment operators
- from cython.operator cimport dereference as deref, preincrement as inc
- cdef extern from "<vector>" namespace "std":
- cdef cppclass vector[T]:
- cppclass iterator:
- T operator*()
- iterator operator++()
- bint operator==(iterator)
- bint operator!=(iterator)
- vector()
- void push_back(T&)
- T& operator[](int)
- T& at(int)
- iterator begin()
- iterator end()
- cdef vector[int] *v = new vector[int]()
- cdef int i
- for i in range(10):
- v.push_back(i)
- cdef vector[int].iterator it = v.begin()
- while it != v.end():
- print(deref(it))
- inc(it)
- del v
Multiple template parameters can be defined as a list, such as [T, U, V]
or [int, bool, char]
. Optional template parameters can be indicatedby writing [T, U, V=*]
. In the event that Cython needs to explicitlyreference the type of a default template parameter for an incomplete templateinstantiation, it will write MyClass<T, U>::V
, so if the class providesa typedef for its template parameters it is preferable to use that name here.
Template functions are defined similarly to class templates, withthe template parameter list following the function name:
- # distutils: language = c++
- cdef extern from "<algorithm>" namespace "std":
- T max[T](T a, T b)
- print(max[long](3, 4))
- print(max(1.5, 2.5)) # simple template argument deduction
Standard library
Most of the containers of the C++ Standard Library have been declaredin pxd files locatedin /Cython/Includes/libcpp.These containers are: deque, list, map, pair, queue, set, stack, vector.
For example:
- # distutils: language = c++
- from libcpp.vector cimport vector
- cdef vector[int] vect
- cdef int i, x
- for i in range(10):
- vect.push_back(i)
- for i in range(10):
- print(vect[i])
- for x in vect:
- print(x)
The pxd filesin /Cython/Includes/libcppalso work as good examples on how to declare C++ classes.
The STL containers coerce from and to thecorresponding Python builtin types. The conversion is triggeredeither by an assignment to a typed variable (including typed functionarguments) or by an explicit cast, e.g.:
- # distutils: language = c++
- from libcpp.string cimport string
- from libcpp.vector cimport vector
- py_bytes_object = b'The knights who say ni'
- py_unicode_object = u'Those who hear them seldom live to tell the tale.'
- cdef string s = py_bytes_object
- print(s) # b'The knights who say ni'
- cdef string cpp_string = <string> py_unicode_object.encode('utf-8')
- print(cpp_string) # b'Those who hear them seldom live to tell the tale.'
- cdef vector[int] vect = range(1, 10, 2)
- print(vect) # [1, 3, 5, 7, 9]
- cdef vector[string] cpp_strings = b'It is a good shrubbery'.split()
- print(cpp_strings[1]) # b'is'
The following coercions are available:
Python type => | C++ type | => Python type |
---|---|---|
bytes | std::string | bytes |
iterable | std::vector | list |
iterable | std::list | list |
iterable | std::set | set |
iterable (len 2) | std::pair | tuple (len 2) |
All conversions create a new container and copy the data into it.The items in the containers are converted to a corresponding typeautomatically, which includes recursively converting containersinside of containers, e.g. a C++ vector of maps of strings.
Iteration over stl containers (or indeed any class with begin()
andend()
methods returning an object supporting incrementing, dereferencing,and comparison) is supported via the for .. in
syntax (including in listcomprehensions). For example, one can write:
- # distutils: language = c++
- from libcpp.vector cimport vector
- def main():
- cdef vector[int] v = [4, 6, 5, 10, 3]
- cdef int value
- for value in v:
- print(value)
- return [x*x for x in v if x % 2 == 0]
If the loop target variable is unspecified, an assignment from type*container.begin()
is used for type inference.
Note
Slicing stl containers is supported,you can do for x in my_vector[:5]: …
but unlike pointers slices,it will create a temporary Python object and iterate over it. Thusmaking the iteration very slow. You might want to avoid slicingC++ containers for performance reasons.
Simplified wrapping with default constructor
If your extension type instantiates a wrapped C++ class using the defaultconstructor (not passing any arguments), you may be able to simplify thelifecycle handling by tying it directly to the lifetime of the Python wrapperobject. Instead of a pointer attribute, you can declare an instance:
- # distutils: language = c++
- from libcpp.vector cimport vector
- cdef class VectorStack:
- cdef vector[int] v
- def push(self, x):
- self.v.push_back(x)
- def pop(self):
- if self.v.empty():
- raise IndexError()
- x = self.v.back()
- self.v.pop_back()
- return x
Cython will automatically generate code that instantiates the C++ objectinstance when the Python object is created and deletes it when the Pythonobject is garbage collected.
Exceptions
Cython cannot throw C++ exceptions, or catch them with a try-except statement,but it is possible to declare a function as potentially raising an C++exception and converting it into a Python exception. For example,
- cdef extern from "some_file.h":
- cdef int foo() except +
This will translate try and the C++ error into an appropriate Python exception.The translation is performed according to the following table(the std::
prefix is omitted from the C++ identifiers):
C++ | Python |
---|---|
bad_alloc | MemoryError |
bad_cast | TypeError |
bad_typeid | TypeError |
domain_error | ValueError |
invalid_argument | ValueError |
ios_base::failure | IOError |
out_of_range | IndexError |
overflow_error | OverflowError |
range_error | ArithmeticError |
underflow_error | ArithmeticError |
(all others) | RuntimeError |
The what()
message, if any, is preserved. Note that a C++ios_base_failure
can denote EOF, but does not carry enough informationfor Cython to discern that, so watch out with exception masks on IO streams.
- cdef int bar() except +MemoryError
This will catch any C++ error and raise a Python MemoryError in its place.(Any Python exception is valid here.)
- cdef int raise_py_error()
- cdef int something_dangerous() except +raise_py_error
If something_dangerous raises a C++ exception then raise_py_error will becalled, which allows one to do custom C++ to Python error “translations.” Ifraise_py_error does not actually raise an exception a RuntimeError will beraised.
There is also the special form:
- cdef int raise_py_or_cpp() except +*
for those functions that may raise either a Python or a C++ exception.
Static member method
If the Rectangle class has a static member:
- namespace shapes {
- class Rectangle {
- ...
- public:
- static void do_something();
- };
- }
you can declare it using the Python @staticmethod decorator, i.e.:
- cdef extern from "Rectangle.h" namespace "shapes":
- cdef cppclass Rectangle:
- ...
- @staticmethod
- void do_something()
Declaring/Using References
Cython supports declaring lvalue references using the standard Type&
syntax.Note, however, that it is unnecessary to declare the arguments of externfunctions as references (const or otherwise) as it has no impact on thecaller’s syntax.
auto Keyword
Though Cython does not have an auto
keyword, Cython local variablesnot explicitly typed with cdef
are deduced from the types of the right handside of all their assignments (see the infer_types
compiler directive). This is particularly handywhen dealing with functions that return complicated, nested, templated types,e.g.:
- cdef vector[int] v = ...
- it = v.begin()
(Though of course the for .. in
syntax is preferred for objects supportingthe iteration protocol.)
RTTI and typeid()
Cython has support for the typeid(…)
operator.
from cython.operator cimport typeid
The typeid(…)
operator returns an object of the type const type_info &
.
If you want to store a type_info value in a C variable, you will need to store itas a pointer rather than a reference:
- from libcpp.typeinfo cimport type_info
- cdef const type_info* info = &typeid(MyClass)
If an invalid type is passed to typeid
, it will throw an std::bad_typeid
exception which is converted into a TypeError
exception in Python.
An additional C++11-only RTTI-related class, std::type_index
, is availablein libcpp.typeindex
.
Specify C++ language in setup.py
Instead of specifying the language and the sources in the source files, it ispossible to declare them in the setup.py
file:
- from setuptools import setup
- from Cython.Build import cythonize
- setup(ext_modules = cythonize(
- "rect.pyx", # our Cython source
- sources=["Rectangle.cpp"], # additional source file(s)
- language="c++", # generate C++ code
- ))
Cython will generate and compile the rect.cpp
file (fromrect.pyx
), then it will compile Rectangle.cpp
(implementation of the Rectangle
class) and link both object filestogether into rect.so
on Linux, or rect.pyd
on windows,which you can then import in Python usingimport rect
(if you forget to link the Rectangle.o
, you willget missing symbols while importing the library in Python).
Note that the language
option has no effect on user provided Extensionobjects that are passed into cythonize()
. It is only used for modulesfound by file name (as in the example above).
The cythonize()
function in Cython versions up to 0.21 does notrecognize the language
option and it needs to be specified as anoption to an Extension
that describes your extension and thatis then handled by cythonize()
as follows:
- from setuptools import Extension, setup
- from Cython.Build import cythonize
- setup(ext_modules = cythonize(Extension(
- "rect", # the extension name
- sources=["rect.pyx", "Rectangle.cpp"], # the Cython source and
- # additional C++ source files
- language="c++", # generate and compile C++ code
- )))
The options can also be passed directly from the source file, which isoften preferable (and overrides any global option). Starting withversion 0.17, Cython also allows passing external source files into thecythonize()
command this way. Here is a simplified setup.py file:
- from setuptools import setup
- from Cython.Build import cythonize
- setup(
- name = "rectangleapp",
- ext_modules = cythonize('*.pyx'),
- )
And in the .pyx source file, write this into the first comment block, beforeany source code, to compile it in C++ mode and link it statically against theRectangle.cpp
code file:
- # distutils: language = c++
- # distutils: sources = Rectangle.cpp
Note
When using distutils directives, the paths are relative to the workingdirectory of the setuptools run (which is usually the project root wherethe setup.py
resides).
To compile manually (e.g. using make
), the cython
command-lineutility can be used to generate a C++ .cpp
file, and then compile itinto a python extension. C++ mode for the cython
command is turnedon with the —cplus
option.
Caveats and Limitations
Access to C-only functions
Whenever generating C++ code, Cython generates declarations of and callsto functions assuming these functions are C++ (ie, not declared as extern "C"
. This is ok if the C functions have C++ entry points, but if they’re Conly, you will hit a roadblock. If you have a C++ Cython module needingto make calls to pure-C functions, you will need to write a small C++ shimmodule which:
{…}
- includes the needed C headers in an extern “C” block
- contains minimal forwarding functions in C++, each of which calls therespective pure-C function
C++ left-values
C++ allows functions returning a reference to be left-values. This is currentlynot supported in Cython. cython.operator.dereference(foo)
is also notconsidered a left-value.