First time here? Check out the FAQ!

Double-clicking a file from finder doesn't open it in Wing when the editor is already active

Using macOS Catalina and Wing Pro, I have the following issue:

When Wing is NOT active and I double-click a .py file somewhere, Wing starts and opens that file.

Whenever Wing is already active, double-clicking a .py file does switch to the Wing window (changes focus to it), but it does not open the file. So any subsequent source files, I have to open from the file menu in Wing. It doesn't matter how many files I have open in Wing at that time (even with all files closed it doesn't work).

Completely removed Wing and all settings files, re-installed and tried again. No joy. This one is pretty recent and I have to say... not a fan.

jrobijns's avatar
asked 2019-12-20 07:49:28 -0500
Wingware Support's avatar
Wingware Support
updated 2020-05-25 08:27:03 -0500
edit flag offensive 0 remove flag close merge delete


I suspect this is Catalina breakage. What version of Wing do you have?

Wingware Support's avatar Wingware Support (2019-12-20 08:25:23 -0500) edit

I'm experiencing the same thing. Everything was working great but then I got a new MacBook and migrated my files to it. The new MacBook is running Catalina, and I made sure to uninstall and then reinstall the very latest version of WIng IDE 101 If Wing is not currently running, then double clicking on a Python file will start up Wing and open the file. But then if I double click on a second file the Wing app comes to the foreground of the desktop, but the file doesn't open!

ProfAB's avatar ProfAB (2019-12-22 18:54:55 -0500) edit

I am also having this issue, is there any possible fix beyond "Catalina Breakage"? I'm using version 5.1.12-1

Catalina also broke my anaconda install, and now Wing also can't select the correct python app for a custom python executable

cheikes's avatar cheikes (2020-04-23 15:07:28 -0500) edit

I think a broken Anaconda caused by installing Catalina can be fixed by removing Anaconda and installing it again. Unfortunately we still don't have a fix for the Catalina file opening issue. The problems with .app packaging on Catalina are definitely quite odd. I keep hoping Apple will fix it since we have not found a work-around, but it's probably something very specific to perhaps shipping a Qt app or something like that. The other issues we were able to solve required bizarre solutions like hiding certain files in a .zip, apparently to "outsmart" Gatekeeper. We will continue to try to solve this, however, although any fix would only be in Wing 7. Sorry about this!

Wingware Support's avatar Wingware Support (2020-04-24 08:54:28 -0500) edit

For my workflow, this really is very annoying. If it's not something you can fix, I can respect that. But boy, this is annoying.

jrobijns's avatar jrobijns (2020-04-29 09:52:55 -0500) edit
add a comment see more comments

1 Answer


This should be fixed in our next release, which will rework how Wing starts in order to avoid the problem. The issue was that Wing's startup script was a shell script and Catalina didn't like that for some reason while it did work with previous macOS versions. The fix will require re-downloading Wing rather than just using Check for Updates since it makes changes in the overall application framework.

Wingware Support's avatar
Wingware Support
answered 2020-05-25 08:26:48 -0500, updated 2020-05-25 08:28:40 -0500
edit flag offensive 0 remove flag delete link


add a comment see more comments

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account. This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss.

Add Answer