search

Crystal03 / google-docs-fs

Automatically exported from code.google.com/p/google-docs-fs
GNU General Public License v2.0
0 stars 0 forks source link

Should use "/usr/bin/env python" as hashbang #38

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
On systems where there are multiple versions of Python installed, 
/usr/bin/python might not be the preferred Python.

What is the expected output? What do you see instead?
Best hashbang for launching Python is "#!/usr/bin/env python". This will launch 
the configured system-wide Python. "#!/usr/bin/python" might not do that.

For example, on Mac OS X, one might use Macports Python, which does not 
overwrite Apple's preinstalled /usr/bin/python.

What version of the product are you using? On what operating system?
svn rev 130

Please provide any additional information below.
None.

Original issue reported on code.google.com by ivuc...@gmail.com on 24 Sep 2010 at 5:03

GoogleCodeExporter commented 9 years ago 
All sorted. The only place was in setup.py which I had missed. It'll be in the 
next revision in about 5 minutes.

If I've missed any others, let me know.

Original comment by d38dm8nw81k1ng@gmail.com on 24 Sep 2010 at 9:53