Handling FutureWarnings in py2exe-generated cons ole-less standalones

Thanks, Roger, and sorry all for what turned out to be a non-wx question.
When I define a warning ignorer, my console-less py2exe app does not crash.

Tim

···

-----Original Message-----
From: Roger Binns [mailto:rogerb@rogerbinns.com]
Sent: Wednesday, June 02, 2004 7:25 PM
To: wxPython-users@lists.wxwidgets.org
Subject: Re: [wxPython-users] Handling FutureWarnings in py2exe-generated
console-less standalones

Tim Black wrote:

eval(compile("x=0xffffffff","","single")) into the top of any wxPython or
PythonCard app and building it into a console-less standalone.

My app has no problems at all despite spewing several futurewarnings,
for exactly the same constants. They are part of the standard code
and not eval'ed.

2. I would like to make my dynamic code execution more robust to these

This is what is in my code, including my sentiments :slight_smile:

    # in production builds we don't need the stupid warnings
    if not __debug__:
        import warnings
        def ignorer(*args, **kwargs): pass
        warnings.showwarning=ignorer

Roger

---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-users-help@lists.wxwidgets.org