changeset 27765:f1fb93eebb1d

util: adjust hgexecutable() to handle frozen Mercurial on OS X sys.executable is "$appbundle/Contents/MacOS/python" when Mercurial is bundled in a frozen app bundle on OS X, so that isn't appropriate. It appears that this was only visible for things launched via util.system(), like external hooks, where $HG was set wrong. It appears that Mercurial also uses 'sys.modules['__main__'].__file__' (here) and 'sys.argv[0]' (in platform.gethgcmd()) to figure out the command to spawn. In both cases, this points to "$appbundle/Contents/Resources/hg", which invokes the system python since "/usr/bin/env python" is on the shebang line. On my system with a screwed up python install, I get an error importing the os module if this script is invoked. We could take the dirname of sys.executable and join 'hg' instead of this if we want to be paranoid, but py2app boostrap is setting the environment variable since 0.1.6 (current version is 0.9), so it seems safe and we might as well use it.
author Matt Harbison <matt_harbison@yahoo.com>
date Sun, 10 Jan 2016 17:56:08 -0500
parents dd0c5f4d1b53
children 198f78a52a2f
files mercurial/util.py
diffstat 1 files changed, 5 insertions(+), 1 deletions(-) [+]
line wrap: on
line diff
--- a/mercurial/util.py	Sun Jan 10 17:49:01 2016 -0500
+++ b/mercurial/util.py	Sun Jan 10 17:56:08 2016 -0500
@@ -907,7 +907,11 @@
         if hg:
             _sethgexecutable(hg)
         elif mainfrozen():
-            _sethgexecutable(sys.executable)
+            if getattr(sys, 'frozen', None) == 'macosx_app':
+                # Env variable set by py2app
+                _sethgexecutable(os.environ['EXECUTABLEPATH'])
+            else:
+                _sethgexecutable(sys.executable)
         elif os.path.basename(getattr(mainmod, '__file__', '')) == 'hg':
             _sethgexecutable(mainmod.__file__)
         else: