1 /* These two macros are basicly Py_BEGIN_ALLOW_THREADS and Py_BEGIN_ALLOW_THREADS
2 * from the other direction. If a Python thread calls a C function
3 * Py_BEGIN_ALLOW_THREADS is used to allow other python threads to run because
4 * we don't intend to call any Python functions.
6 * These two macros are used whenever a C thread intends to call some Python
7 * function, usually because some registered callback was triggered.
8 * Just like Py_BEGIN_ALLOW_THREADS it opens a block so these macros have to be
9 * used in pairs. They aquire the GIL, create a new Python thread state and swap
10 * the current thread state with the new one. This means this thread is now allowed
11 * to execute Python code. */
13 #define CPY_LOCK_THREADS {\
14 PyGILState_STATE gil_state;\
15 gil_state = PyGILState_Ensure();
17 #define CPY_RETURN_FROM_THREADS \
18 PyGILState_Release(gil_state);\
21 #define CPY_RELEASE_THREADS \
22 PyGILState_Release(gil_state);\
25 /* Python 2.4 has this macro, older versions do not. */
27 #define Py_VISIT(o) do {\
30 _vret = visit((o), arg);\
37 /* Python 2.4 has this macro, older versions do not. */
39 #define Py_CLEAR(o) do {\
47 PyObject_HEAD /* No semicolon! */
48 PyObject *parent; /* Config */
49 PyObject *key; /* String */
50 PyObject *values; /* Sequence */
51 PyObject *children; /* Sequence */
54 PyTypeObject ConfigType;
57 PyObject_HEAD /* No semicolon! */
59 char host[DATA_MAX_NAME_LEN];
60 char plugin[DATA_MAX_NAME_LEN];
61 char plugin_instance[DATA_MAX_NAME_LEN];
62 char type[DATA_MAX_NAME_LEN];
63 char type_instance[DATA_MAX_NAME_LEN];
66 PyTypeObject PluginDataType;
70 PyObject *values; /* Sequence */
74 PyTypeObject ValuesType;
79 char message[NOTIF_MAX_MSG_LEN];
82 PyTypeObject NotificationType;