[Python-Dev] cpython: threading.RLock._acquire_restore() now raises a TypeError instead of a (original) (raw)
Serhiy Storchaka storchaka at gmail.com
Fri Jan 3 08:59:23 CET 2014
- Previous message: [Python-Dev] 2.x vs 3.x survey results
- Next message: [Python-Dev] cpython: threading.RLock._acquire_restore() now raises a TypeError instead of a
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
02.01.14 13:54, victor.stinner написав(ла):
http://hg.python.org/cpython/rev/9a61be172c23 changeset: 88249:9a61be172c23 user: Victor Stinner <victor.stinner at gmail.com> date: Thu Jan 02 12:47:24 2014 +0100 summary: threading.RLock.acquirerestore() now raises a TypeError instead of a SystemError when it is not called with 2 arguments
- if (!PyArgParseTuple(arg, "kl:acquirerestore", &count, &owner)) + if (!PyArgParseTuple(args, "(kl):acquirerestore", &count, &owner)) return NULL;
Please don't use "(...)" in PyArg_ParseTuple, it is dangerous (see issue6083 [1]).
[1] http://bugs.python.org/issue6083
- Previous message: [Python-Dev] 2.x vs 3.x survey results
- Next message: [Python-Dev] cpython: threading.RLock._acquire_restore() now raises a TypeError instead of a
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]