Comment 4 for bug 389065

We now have a branch (sitepackages-ng-1) merged that addresses the concerns Francis raises in comment #2. With that branch, when I compare the sys.path for bin/py and bin/harness, I get different order for the paths, but the exact same eggs in a set comparison.

I tried the PYTHONSTARTUP approach that Stuart suggested. This works well for running bin/py in the interactive prompt but PYTHONSTARTUP has no affect on using bin/py to run scripts (it is described in ``python -h`` as "PYTHONSTARTUP: file executed on interactive startup (no default)"). Therefore it does not work for all of our use cases.

I'm going to optimistically declare this fixed via my buildout branch, and stick with the use of PYTHONPATH.

If we have further problems with bin/py, we can investigate using the Python-interpreter-alike that zc.recipe.egg can produce. It does not and cannot support all of the options that the normal Python binary offers, and we use some of them in the Makefile, so it might need some care in the switch.