Author larry
Recipients benjamin.peterson, georg.brandl, ghaering, larry, r.david.murray, serhiy.storchaka
Date 2015-05-08.14:25:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1431095122.22.0.284108947425.issue20274@psf.upfronthosting.co.za>
In-reply-to
Content
I'm gonna fix this now.  (I'm cleaning up some old issues I filed on the bug tracker this morning.)

For 3.4, I'm just removing the PyObject *kwargs for those three functions that don't actually accept keyword arguments (METH_VARARGS) and aren't passed that parameter.  That's a bug plain and simple, it's relying on undefined behavior, and it's better that we fix it.

For 3.5. I'm adding a call to _PyArg_NoKeywords() to pysqlite_connection_call.  Previously it simply ignored any/all keyword arguments; now it will complain if it is passed any.  We don't need a deprecation cycle for that.
History
Date User Action Args
2015-05-08 14:25:22larrysetrecipients: + larry, georg.brandl, ghaering, benjamin.peterson, r.david.murray, serhiy.storchaka
2015-05-08 14:25:22larrysetmessageid: <1431095122.22.0.284108947425.issue20274@psf.upfronthosting.co.za>
2015-05-08 14:25:22larrylinkissue20274 messages
2015-05-08 14:25:22larrycreate