On 2013-02-08 02:30:28 +0000, Craig Hess said:
On Thu, Feb 7, 2013 at 8:13 PM, K.-Michael Aye kmichael.aye@gmail.com wrote: I guess you meant to save that as a script file ***.sh and then hit Cmd-R? In that case I get:
Press Ctrl-R on the same line that you have: echo $TM_PYTHON The line is passed to the shell, and the results of the command are appended on the lines beneath it. Also useful is to execute "env" in this way. It'll show all the variables available to TextMate and their values.
I see, ok, did that, still the same:
echo $TM_PYTHON /Library/Frameworks/Python.framework/Versions/Current/bin/python
Summarizing the weirdness:
When I do NOT have a shebang, it uses the above linked interpreter. ONLY when I use ---- #!/usr/bin/env python ---- as shebang, the WRONG interpreter (OSX default Python) is being used, despite the fact that when I am using "/usr/bin/env python" in a Terminal I again get the one I want:
(develop+)[maye@alpha1 .../luna1disk/src/diviner]$ /usr/bin/env python Enthought Python Distribution -- www.enthought.com Version: 7.3-2 (32-bit)
Python 2.7.3 |EPD 7.3-2 (32-bit)| (default, Apr 12 2012, 11:28:34) [GCC 4.0.1 (Apple Inc. build 5493)] on darwin Type "credits", "demo" or "enthought" for more information.
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate