-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/11/10 13:55, Nick Coghlan wrote:
> Under -We, PyErr_Warn raises an exception rather than printing to
> stdout. That exception is clobbered by the immediately following call
> to PyErr_Clear.
> Since you *only* hit that branch under -We in the fir
On Fri, Nov 5, 2010 at 11:12 AM, Jesus Cea wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 05/11/10 01:36, Benjamin Peterson wrote:
>>> I don't know why.
>>
>> Are you passing -3 -Wall?
>
> I am passing "-3 -Werror", to induce the error control I have committed.
Under -We, PyErr_W
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/11/10 01:36, Benjamin Peterson wrote:
>> I don't know why.
>
> Are you passing -3 -Wall?
I am passing "-3 -Werror", to induce the error control I have committed.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...
2010/11/4 Jesus Cea :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi all. I just committed r86180, but there is something I don't like.
>
> If you read the tests I did (by hand)at
> http://bugs.python.org/issue9675#msg120462 , python should show the
> unraisable and THEN the "C API unavai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all. I just committed r86180, but there is something I don't like.
If you read the tests I did (by hand)at
http://bugs.python.org/issue9675#msg120462 , python should show the
unraisable and THEN the "C API unavailable" warning, but it is not
showin
