On Aug 12, 6:28 pm, "Edward K. Ream" <[email protected]> wrote:
> [This] is the best that can be done::
>
> exec(g.findTestScript(c,'@common leoRst test code'))
This is pretty damn good. In other Python scripting environments, one
would presumably get the shared code using import or execfile. This
is a much more convenient solution: I can update the common code
without changing any file at all.
Indeed, I want to do this precisely because I do not want to have to
do something like this:
import leo.core.leoTest as leoTest
leoTest.Hello('Bob')
It's not that this is more typing, it's that it is considerably less
dynamic. Worse, the common code belongs with the unit tests, not in
leoTest.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.
