5 Commits

Author	SHA1	Message	Date
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
Brian Warner	25ff9e1f97	complete the Introducer changes, separate out vdrive access, make everything work again	2007-03-27 16:12:11 -07:00
Brian Warner	1264d77fd5	hush a pyflakes warning	2007-03-22 22:22:00 -07:00
Brian Warner	ca33c8f848	more work on a memory-footprint test program	2007-03-12 16:28:37 -07:00
Brian Warner	1e25c9e897	start work on a memory-measuring test tool	2007-03-08 18:12:24 -07:00