Are these problems due to (a) python 3 (b) different OS or (c)
differing configuration (e.g., $HOME/.leo/myLeosettings.lo)? If
python 3, I'll be more motivated to update to Fedora 13, which has
python 3 packages available. If different OS (e.g., Mac using \r for
line endings) then I'll have to get supermotivated - the 8 year old
minimac I've got access to has been turned off for two years, and I'm
not sure what hardware surprises I'll suffer as I try to update its OS
to something recent. If it's a matter of settings, then I need to
account for that in the initialization before the tests, and I also
need to write different tests for the other reasonable
initialization. I already know from the coverage tool that there are
a number of features (tangleCommands.print_mode == verbose, CWEB
escape codes, etc.) that are untested.
- Stephen
On Jun 30, 2:15 pm, "Edward K. Ream" <[email protected]> wrote:
> On Wed, Jun 30, 2010 at 1:05 PM, Edward K. Ream <[email protected]> wrote:
>
> > On Wed, Jun 30, 2010 at 11:43 AM, thyrsus <[email protected]> wrote:
> >> I'm now getting one unit test failure, but I don't think it's my code,
> >> so I'm pushing:
>
> > I thought I had fixed this. I'll look again.
>
> The fix is on the trunk at rev 3141. This rev also adds some parens
> to print statements in leoTest.py so that Leo will once again run with
> Python 3k.
>
> On my machine 7 @root-related unit tests continue to fail, but I'm not
> too worried about that just now.
>
> 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.
