For the last several days I've been working on the infrastructure
behind Leo's importers.  This is intertwined with Leo's unit-testing
code, mostly via g.app.unitTestDict.

As I did so, I have found several problems.

1. As discussed in another thread, I have improved the support for
running tests externally.

2. As another violation of the DRY principle, I have discovered that
Leo sometimes, but not always, makes the text of the script or unit
tests available to Python's pdb module (g.pdb).  It's essential that
g.pdb *always* shows the relevant text.  That's my next task.

I have posted some urgent bug fixes without creating new unit tests (I
always do run all the existing tests).  I'll soon attempt to cover all
recent changes with new tests.

Slow but slow indeed.

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.

Reply via email to