Author n8gray
Recipients
Date 2004-10-04.20:16:42
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=121553

The issue is that sometimes you *do* care where python is installed, and 
you want to be sure to get the system python and not, for example, the 
Fink python.  At the moment, the only solution is to use a gangly #! line 
like:
#! /System/Library/Frameworks/Python.framework/Resources/
Python.app/Contents/MacOS/Python
and you'll only figure that out if you're clever enough to understand why 
#!/usr/bin/python works but #!/usr/bin/pythonw doesn't.

Mainly, it's just needlessly confusing to have a python interpreter that 
works from the command line but doesn't work in a #! line.  It's 
unfortunate that the distinction between python and pythonw is 
necessary, but as long as it is then it would be nice if at least pythonw 
was able to act as a drop-in replacement for python.  It's pretty simple 
to make it work as expected, so why not do it, for the sake of 
consistency?
History
Date User Action Args
2007-08-23 15:40:03adminlinkissue1038911 messages
2007-08-23 15:40:03admincreate