On Sun, 27 Nov 2011 18:19:53 -0000
HansBKK <email address hidden> wrote:
> The only instance of launchLeo.py is under /Lib/site-packages/leo-
> editor4, which totals 28.8 MB as a result of the export command I cited.
>
> Running Windows 7, installed all prerequisites from MSI's and then
> copied to my "Portable Python" setup, which is where I ran bazaar to
> install Leo I only executed the two bazaar commands above.
>
> Scripts looks like this:
> leo-editor
> └───.bzr
> ├───branch-lock
> └───repository
I guess there are lots of ways you could "run Leo from bzr", but the
method the docs. intend to describe does not require `bzr export`,
and does not install under site-packages. It doesn't really
"install" at all, it just creates a directory "leo-editor" wherever
you run the bzr command. Leo does not end up on the system executable
path or the python module search path. When you run Leo by running the
launchLeo.py script in .../leo-editor/ it finds all the leo.foo.bar
modules it needs because the leo folder is in the same folder as
launchLeo.py.
There should never be any need to look inside the .bzr directory.
On Sun, 27 Nov 2011 18:19:53 -0000
HansBKK <email address hidden> wrote:
> The only instance of launchLeo.py is under /Lib/site- packages/ leo-
> editor4, which totals 28.8 MB as a result of the export command I cited.
>
> Running Windows 7, installed all prerequisites from MSI's and then
> copied to my "Portable Python" setup, which is where I ran bazaar to
> install Leo I only executed the two bazaar commands above.
>
> Scripts looks like this:
> leo-editor
> └───.bzr
> ├───branch-lock
> └───repository
I guess there are lots of ways you could "run Leo from bzr", but the
method the docs. intend to describe does not require `bzr export`,
and does not install under site-packages. It doesn't really
"install" at all, it just creates a directory "leo-editor" wherever
you run the bzr command. Leo does not end up on the system executable
path or the python module search path. When you run Leo by running the
launchLeo.py script in .../leo-editor/ it finds all the leo.foo.bar
modules it needs because the leo folder is in the same folder as
launchLeo.py.
There should never be any need to look inside the .bzr directory.
Cheers -Terry