Re: [Python-Dev] cpython: threading.RLock._acquire_restore() now raises a TypeError instead of a

2014-01-04 Thread Armin Rigo
Hi Serhiy, On Fri, Jan 3, 2014 at 8:59 AM, Serhiy Storchaka storch...@gmail.com wrote: +if (!PyArg_ParseTuple(args, (kl):_acquire_restore, count, owner)) Please don't use (...) in PyArg_ParseTuple, it is dangerous (see issue6083 I think that in this case it is fine, because the k and l

Re: [Python-Dev] cpython: threading.RLock._acquire_restore() now raises a TypeError instead of a

2014-01-03 Thread Serhiy Storchaka
02.01.14 13:54, victor.stinner написав(ла): http://hg.python.org/cpython/rev/9a61be172c23 changeset: 88249:9a61be172c23 user:Victor Stinner victor.stin...@gmail.com date:Thu Jan 02 12:47:24 2014 +0100 summary: threading.RLock._acquire_restore() now raises a TypeError instead

Re: [Python-Dev] cpython: threading.RLock._acquire_restore() now raises a TypeError instead of a

2014-01-03 Thread Victor Stinner
Hi, 2014/1/3 Serhiy Storchaka storch...@gmail.com: -if (!PyArg_ParseTuple(arg, kl:_acquire_restore, count, owner)) +if (!PyArg_ParseTuple(args, (kl):_acquire_restore, count, owner)) return NULL; Please don't use (...) in PyArg_ParseTuple, it is dangerous (see issue6083

Re: [Python-Dev] cpython: threading.RLock._acquire_restore() now raises a TypeError instead of a

2014-01-03 Thread Victor Stinner
2014/1/3 Victor Stinner victor.stin...@gmail.com: 2014/1/3 Serhiy Storchaka storch...@gmail.com: -if (!PyArg_ParseTuple(arg, kl:_acquire_restore, count, owner)) +if (!PyArg_ParseTuple(args, (kl):_acquire_restore, count, owner)) return NULL; Please don't use (...) in