mcow
commented
5 years ago Here is a simple script that loads the evented COM object and does nothing but PumpWaitingMessages() until the OnShutdown() event is triggered by closing the application.
MM5_idlehandler.zip
The equivalent script works as expected with version 4 of MediaMonkey, when loading the version-specific CLSID. makepy on that version's library also works fine. Note that the script is intended to debug an issue with MediaMonkey's handling of the event object; there is a problem in version 4 and I wanted to determine if the problem persists in version 5.
Trying to register a new application's library. Running makepy presents the library-selector dialog and the new app is there. When I select it, I get the Generating To... and Building definitions... messages, then (at command line) returns to prompt, or (in PythonWin) PythonWin suddenly closes. The catalog file is present but empty (0 bytes). If I delete the empty catalog and attempt to access the library in my script, the zero-byte catalog is again created, and the script simply exits prematurely. In no case do I get diagnostic information.
Expected behavior and actual behavior. Expected: makepy generates a type registry catalog for the application (or, if failing, at least gives information why). Actual: makepy generates a zero-byte registry catalog and terminates with extreme prejudice.
Steps to reproduce the problem. Install MediaMonkey 5 (beta) from http://www.mediamonkey.com/beta/MediaMonkey_5.0.0.2182_Debug.exe (this is a debug build, and the latest as of this bug report; for updates, see the forum.) Run makepy Select "MediaMonkey5 Library (1.0)" and OK.
Version of Python and pywin32 Python 3.6.6, pywin32 224, Windows 10 Home 1809