> > Will add `leo.egg-link` in `PYTHONHOME/Lib/site-packages` which
> > enables `import leo` to work. The egg-link file contains the path to
> > the code directory, so editing sys.path shouldn't be needed.
>
> I searched but couldn't find an example copy of leo.egg-link, and as I
> mentioned, prefer not to use pip.
>
My Windows egg-link file (PYTHONHOME\Lib\site-packages\leo.egg-link):
D:\code-maphew\leo-editor
.
An alternative is to sym- or hardlink "{extracted code
location}/leo-editor-master/leo" to "$PYTHONHOME/Lib/site-packages/leo".
In both cases to launch Leo from command line a wrapper needs to be put in
"$PYTHONHOME/Scripts" that resembles launchLeo.py from repo root:
#!/usr/bin/env python
""" Leo launcher script A minimal script to launch leo """
import leo.core.runLeo
leo.core.runLeo.run()
Also important to know is that only ./leo and subfolders count for
anything. The repo root folder is invisible and ignored.
Hope that helps!
-matt
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/leo-editor/af5ffdac-f4f0-46e4-a15b-d4a1ca03343e%40googlegroups.com.
