Who sets _DEBUG? Wouldn't manually undeffing _DEBUG be just as easy as
manually setting __PYX_WIN_DEBUG? Disclaimer: I've never developed
Python on Windows, but it seems that Nikita's solution is simpler.
On Thu, Jul 25, 2013 at 12:11 PM, WL wrote:
> On 25.07.2013 18:01, Robert Bradshaw wrote:
>>
On 25.07.2013 18:01, Robert Bradshaw wrote:
On Thu, Jul 18, 2013 at 6:24 AM, Wolfgang wrote:
Hi,
I tried to submit a improvement for the Windows build but the tracker is not
accessible without a login.
This is to prevent spam.
On Windows if someone does a Debug build of an extension the fla
On Thu, Jul 18, 2013 at 6:24 AM, Wolfgang wrote:
> Hi,
>
> I tried to submit a improvement for the Windows build but the tracker is not
> accessible without a login.
This is to prevent spam.
> On Windows if someone does a Debug build of an extension the flag _DEBUG is
> set and so the Python Int
ng
> Message: 1
> Date: Wed, 24 Jul 2013 21:15:49 +0600
> From: "Nikita Nemkin"
> To: "Core developer mailing list of the Cython compiler"
>
> Subject: Re: [Cython] Windows Debug build improvement
> Message-ID:
> Content-Type: text/plain; charset=wi
On Thu, 18 Jul 2013 19:24:21 +0600, Wolfgang wrote:
Hi,
I tried to submit a improvement for the Windows build but the tracker is
not
accessible without a login.
On Windows if someone does a Debug build of an extension the flag _DEBUG
is
set and so the Python Interpreter sets Py_DEBUG and
Hi,
I tried to submit a improvement for the Windows build but the tracker is not
accessible without a login.
On Windows if someone does a Debug build of an extension the flag _DEBUG is
set and so the Python Interpreter sets Py_DEBUG and for all extension modules
"_d" is appended to load the debug
