On Fri, Mar 9, 2012 at 9:57 AM, Ville M. Vainio <[email protected]> wrote:
> On Fri, Mar 9, 2012 at 5:50 PM, Edward K. Ream <[email protected]> wrote:
>
>> How do you feel about importing leoGlobals at the top level now?
>
> I'm ok with that, but don't really see a benefit. Code that can run
> without Leo running is more valuable than one that can't, so I'd
> rather leave it out for quick tests in the future.
I see. I was confused by this import::
try:
import leo.plugins.leofts as leofts
except ImportError:
leofts = None
But we can't use this approach for leoGlobals: g.toUnicode is
necessary for Python 3k. It might be best to copy g.toUnicode (and
its several helpers) into bigdash.py.
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en.
