On Mon, 9 Dec 2013 12:53:37 -0600 "Edward K. Ream" <[email protected]> wrote:
> If none of us can remember which is which, why not just use > leo/extensions (so g.importExtension continues to work without change) and > be done with it? The two "namespaces" just seem to be causing confusion. Initially I thought no, the leo-specific (extensions) / non-leo-specific (external) split is useful and worth keeping, but then I realized that you'll definitely want the non-leo-specific python modules to be on sys.PATH, which implies they need to go in extensions to work with g.importExtension .. so maybe just collapsing to extensions with clear docs as to where things come from is best. I wouldn't think to use g.importExtension, I'd import from leo.extentions / leo.external. Cheers -Terry -- 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
