Zooko O'Whielacronx 4b4f5bbcba change #!/usr/bin/python to #!/usr/bin/env python ... Note that using "whatever version of python the name 'python' maps to in the current shell environment" is more error-prone that specifying which python you mean, such as by executing "/usr/bin/python setup.py" instead of executing "./setup.py". When you build tahoe (by running "make") it will make a copy of bin/allmydata-tahoe in instdir/bin/allmydata-tahoe with the shebang line rewritten to execute the specific version of python that was used when building instead of to execute "/usr/bin/env python". However, it seems better that the default for lazy people be "whatever 'python' means currently" instead of "whatever 'python' meant to the manufacturer of your operating system".		2007-03-29 14:01:28 -07:00
..
figleaf2el.py	change #!/usr/bin/python to #!/usr/bin/env python	2007-03-29 14:01:28 -07:00
figleaf2html	move figleaf2html and figleaf_htmlizer.py into our tree, for easier customization	2007-01-03 22:06:51 -07:00
figleaf.el	figleaf.el: add code to auto-enable the annotation mode for all source files	2007-01-18 01:00:11 -07:00
getmem.py	change #!/usr/bin/python to #!/usr/bin/env python	2007-03-29 14:01:28 -07:00