[ python-Bugs-1383644 ] MacOS.WMAvailable() doesn't launch Python.app properly

[SourceForge.net]

Bugs item #1383644, was opened at 2005-12-17 17:12
Message generated for change (Comment added) made by jackjansen
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1383644&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Macintosh
Group: Platform-specific
>Status: Closed
>Resolution: Works For Me
Priority: 5
Submitted By: has (hhas)
Assigned to: Jack Jansen (jackjansen)
Summary: MacOS.WMAvailable() doesn't launch Python.app properly

Initial Comment:
Running the following on Apple-installed Python 2.3.5 on OS 10.4.3:

~ has$ pythonw
Python 2.3.5 (#1, Mar 20 2005, 20:38:20)
[GCC 3.3 20030304 (Apple Computer, Inc. build 1809)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import MacOS
>>> MacOS.WMAvailable()
True

a Python.app process starts to launch as expected; however its icon 
remains bouncing indefinitely in the Dock. Additional prodding, e.g.:

>>> import Carbon.Evt
>>> Carbon.Evt.WaitNextEvent(0,0)
(0, (0, 0, 1141622, (751, 225), 128))

causes it to finish launching as expected (Dock icon stops bouncing, 
small black triangle appears next to it). Third-party has confirmed this 
problem.

Might be a problem with WMAvailable(), might be a problem in 
Python.app. Don't know enough Carbon to determine this myself.

----------------------------------------------------------------------

>Comment By: Jack Jansen (jackjansen)
Date: 2005-12-20 12:10

Message:
Logged In: YES 
user_id=45365

This is not a bug: this is expected behaviour:-)

Note that nothing is "launched" by WMavailable() or WaitNextEvent(): the only 
thing these calls do is signal the existence of pythonw (or actually 
Python.app) to the window manager.

Before WMAvailable() is called the window manager knows nothing about 
Python.app, so nothing is shown in the dock. WMavailable() causes the very 
first WM call, which (among other things) make the dock icon appear and 
start bouncing. The "end of bouncing" happens when the WM notices the app 
has gone into its event loop, which is indeed signalled by calling WNE() or 
something similar.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1383644&group_id=5470