I suppose the explanation for what you are doing(or should be) should
go here then to make it more obvious.
~/ $ cd newproject
~/newproject $ /usr/bin/python2.7 bootstrap.py --distribute
pyramid_appengine merely generates a buildout directory based on
templates, once the project is generated, it's does not have
pyramid_appengine as a dependency.
installing pyramid/associated libs like pyramid_appengine in a
virtualenv is generally good practice so that you avoid polluting your
system install of python
maybe it's a miss on the expected experience level of the reader. If I
documented why you should use buildout and why you should use
virtualenv and why appengine apps are structured the way they are it
would be very long documentation that would be quickly out of date
because it would have to be copied from other sources.
So I'm open to suggestions on how to make this bit clearer, but I'm
not too keen on documenting virtualenv, appengine apps and buildout.
especially since all 3 are in a state of flux at the moment.
Thomas G. Willis