Description
Originally reported by: Anonymous
There is a long tradition of python having a "pythonw", used to run scripts / programs that use the Windowing system.
On most *nix systems, pythonw is a no-op, aliased to the same executable.
On Windows, I've lost track, but I think it is different.
On the Mac, GUI programs need to be run from a properly defined application package. So there is a "python", and "pythonw". However, for years (and many versions) the python.org build of python has made pythonw aliased to python, so it's a non-issue there.
But the Anaconda build of python DOES have a distinct python and pythonw, and homebrew or macports may also.
So, unless pythonw has been officially deprecated, then setuptools should support it.
This will probably be as simple as changing the shebang line in the generated launch scripts to use "pythonw" for gui_script entry points.