On Sep 25, 2006, at 5:24 PM, David Binger wrote:

> Okay, here is what I propose.
>
> Change Site.get_sites() to look more carefully for sites,
> using every path in qp.sites.__path__, not just the first one.
>
> Modify qp.site.__init__.py to set the path to be:
> ${QP_SITES}
> ~/qp_sites
> ~/.qp_sites
> ~/.qp_sites
> /var/qp_sites
> 

Sounds great.

So now sites.__init__.py belongs to the qp installation, and not to the
user's qp_sites ?

> Also add a -base= option to the 'qp' command,
> which sets QP_SITES to be the directory where python finds the
> mysites_package.

Seems good.

> Add an __init__.py to qp.demo, so that the demo sites can, if
> desired, be run using "qp --base=qp.demo start"

Very good idea. This would therefore imply:
- No need to explicitly "install" the demos with each update of qp
- Must run the demos with a user that will have write access to
qp.demo... unless the demos are configured to use a writable and
throwaway var_directory, such as under /tmp or under ~/qp_tmp or so. Or
would you just make the var dir for each demo to be writable by all?

> This also simplifies the installation procedure, since sites will
> be a directory instead of a link.

Yes, that's excellent.