This was inconsistent after
dd7baa2ae2f98d5c1e82fa97f223925025da5ca0,
and may be the cause of test errors on s390x. (The change to
py_ldb_dn_set_component() kept the Py_ssize_t type for 'size' without
setting the PY_SSIZE_T_CLEAN macro to have PyArg_ParseTuple() expect
a Py_ssize_t. Instead, PyArg_ParseTuple() expected an int.
See in particular debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808769
Signed-off-by: Andrew Bartlett <abartlet@samba.org>
Reviewed-by: Jelmer Vernooij <jelmer@samba.org>
char *name;
int err;
uint8_t *value;
- int size = 0;
+ Py_ssize_t size = 0;
if (!PyArg_ParseTuple(args, "sz#", &name, (const char**)&value, &size))
return NULL;
static PyObject *py_binary_encode(PyObject *self, PyObject *args)
{
char *str, *encoded;
- int size = 0;
+ Py_ssize_t size = 0;
struct ldb_val val;
PyObject *ret;