ACTIVITY SUMMARY (2013-12-27 - 2014-01-03)
Python tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open4348 (+16)
closed 27538 (+18)
total 31886 (+34)
Open issues wit
2014/1/3 Zachary Ware :
> The above-quoted parts of this changeset caused several compiler
> warnings due to unused variables. On 32-bit Windows:
> (...)
> I believe this should fix it, but I'll leave it up to you to confirm
> that, Victor :)
Oh, I didn't notice these warnings. I fixed them, than
On Fri, Jan 3, 2014 at 6:01 AM, victor.stinner
wrote:
> http://hg.python.org/cpython/rev/d453c95def31
> changeset: 88271:d453c95def31
> user:Victor Stinner
> date:Fri Jan 03 12:53:47 2014 +0100
> summary:
> add unicode_char() in unicodeobject.c to factorize code
>
> files:
>
2014/1/3 Victor Stinner :
> 2014/1/3 Serhiy Storchaka :
>>> -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 dan
Hi,
2014/1/3 Serhiy Storchaka :
>> -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
> [1])
02.01.14 13:54, victor.stinner написав(ла):
http://hg.python.org/cpython/rev/9a61be172c23
changeset: 88249:9a61be172c23
user:Victor Stinner
date:Thu Jan 02 12:47:24 2014 +0100
summary:
threading.RLock._acquire_restore() now raises a TypeError instead of a
SystemError when it
