Avoiding bad call flags with python 3.8, using METH_NOARGS instead of zero.
authorTorsten Fohrer <torsten.fohrer@sbe.de>
Sun, 15 Dec 2019 15:58:40 +0000 (16:58 +0100)
committerKarolin Seeger <kseeger@samba.org>
Thu, 19 Dec 2019 09:57:24 +0000 (09:57 +0000)
(C) SBE network solutions GmbH

BUG: https://bugzilla.samba.org/show_bug.cgi?id=14209

Signed-off-by: Torsten Fohrer <torsten.fohrer@sbe.de>
Reviewed-by: Douglas Bagnall <douglas.bagnall@catalyst.net.nz>
Reviewed-by: Ralph Boehme <slow@samba.org>
Autobuild-User(master): Ralph Böhme <slow@samba.org>
Autobuild-Date(master): Wed Dec 18 14:33:58 UTC 2019 on sn-devel-184

(cherry picked from commit f0eb1e623f76d3dbd0c22f96cabebd1041c147df)

source4/auth/gensec/pygensec.c

index d27fe28648a807bfe9e6f8fc4aca7974041b3f6c..c9f3fd3b4893268e17f7087cea9340a51b488e18 100644 (file)
@@ -659,7 +659,7 @@ static PyMethodDef py_gensec_security_methods[] = {
                "S.have_feature()\n Return True if GENSEC negotiated a particular feature." },
        { "set_max_update_size",  (PyCFunction)py_gensec_set_max_update_size, METH_VARARGS,
                "S.set_max_update_size(max_size) \n Some mechs can fragment update packets, needs to be use before the mech is started." },
-       { "max_update_size",  (PyCFunction)py_gensec_max_update_size, 0,
+       { "max_update_size",  (PyCFunction)py_gensec_max_update_size, METH_NOARGS,
                "S.max_update_size() \n Return the current max_update_size." },
        { "update",  (PyCFunction)py_gensec_update, METH_VARARGS,
                "S.update(blob_in) -> (finished, blob_out)\nPerform one step in a GENSEC dance.  Repeat with new packets until finished is true or exception." },