PythonWin Debugger

[Dale Strickland-Clark]

It's OK. Ignore me.

I've found a bit more on __debug__. This is how it's supposed to work.

That's pretty useless, isn't it?

So back to my original question:

How do I know if I'm being debugged?

:-)

Dale Strickland-Clark <dale at out-think.NOSPAMco.uk> wrote:

>Thanks for that.
>
>I found assert() in the docs and it mentions a __debug__ variable,
>which is what I was looking for. However, It alwasy seems to be TRUE -
>even when running outside the developement environment.
>
>Any idea why?
>
>Thanks
>
>
>
>"Franz GEIGER" <fgeiger at datec.at> wrote:
>
>>You can use assert(), which can be activated / deactivated by environment.
>>
>>Regards
>>Franz GEIGER
>>
>>Dale Strickland-Clark <dale at out-think.NOSPAMco.uk> schrieb in im
>>Newsbeitrag: 23ogtsccrfllg97b33rc9js65o2oqi5a96 at 4ax.com...
>>> Is there something I can test in a Python program to see if its
>>> running under the debugger? I just want to enable some debugging
>>> messages.
>>>
>>> Also, under the Tools menu, there is a "Python Trace Collector".
>>> Anyone know what this is? I've never seen anything appear on it. If I
>>> could direct debugging messages here, leaving the Interactive window
>>> for normal output, that would be really handy.
>>>
>
>
>Dale Strickland-Clark
>Out-Think Ltd
>Business Technology Consultants
>

Dale Strickland-Clark
Out-Think Ltd
Business Technology Consultants