Status report: I want to be back soon :-)

[Edward K. Ream]

Earlier this year I promised Kent that I would alternate my attention between Leo and the static type checking project: https://groups.google.com/forum/?fromgroups#!forum/python-static-type-checking I haven't kept that promise.  In fact, I have been devoting *all* my attention to the type-checking project.  I'm not even playing the piano much.  When I'm not actively working on the project I'm letting my non-conscious mind work on the problem to the exclusion of everything else.

I don't seem to have a choice: if I were to divide my attention now I would lose all the momentum that I have so laboriously built up.  Happily, I am guessing that only a few weeks, or even a few days, may suffice to reach one last essential breakthrough.  Just this morning I saw where to look for the Aha.  Details later today in the other project.

Yes, many interesting and important projects are piling up in the Leo world.  I apologize for the interruption and ask for your understanding.  I do hope to get back to you all sooner rather than later.  I will not be happy if the work on type checking lasts much beyond the new year.

Edward

P.S.  I have been looking for ways that the type-checking work can contribute to Leo.   Yesterday I found one.  I wrote a script that converts @test nodes to typical unit tests (subclasses of unittest.TestCase).  The script writes these converted tests to one or more external files.  This is a remarkably simple script; you could easily change it to make it work just as you please. More details at: https://groups.google.com/forum/?fromgroups=#!topic/python-static-type-checking/8y3UFlRE0dY  I'll be adding this script to scripts.leo today.

EKR

[Edward K. Ream]

On Thursday, December 20, 2012 10:27:48 AM UTC-6, Edward K. Ream wrote:

> I do hope to get back to you all sooner rather than later.

At last I am feeling good physically: strength and flexibility work has eliminated the intense pains I suffered much of this year.  As a result, I have much more energy for invention and programming.  This energy should carry over to the Leo project :-)

EKR

[Edward K. Ream]

On Thu, Dec 20, 2012 at 10:27 AM, Edward K. Ream <edre...@gmail.com> wrote:

> I'll be adding this script to scripts.leo today.

Done at rev 5540.  You will find it at the top level of scripts.leo. Here is the script's docstring:

QQQQQ
    This script transliterates @test nodes into .py file. The two main ways of
    using this script are as follows::
   
        TestWriter(c,path='test').run(fn='unit_tests.py') # writes one file
        TestWriter(c,path='test').run(fn=None)            # writes separate files.
        
    The first writes all tests to test/unit_tests.py; the second writes each
    unit test to a separate .py file in the test directory.
   
    The script imports each written file and reports any syntax errors.
   
    This is a straightforward script; it should be easy to modify it to suit
    individual needs.
QQQQQ

One last word.  This could be an essential script for some people.  It allows people to use Leo's @test nodes for their own use, while at the same time creating traditional unit tests for those who do not use Leo.

Edward

[Matt Wilkie]

One last word.  This could be an essential script for some people.  It allows people to use Leo's @test nodes for their own use, while at the same time creating traditional unit tests for those who do not use Leo.

The prospect of this is welcome. I'm (very slowly) working my way through a python course. For the unittest module, part 1, I ended up abandoning Leo in order to conform to the curriculum requirements.

> Yes, many interesting and important projects are piling up in the Leo world.  I apologize for the interruption and ask for your understanding

That's easy for me to give. :) You're dedication to Leo is long standing and quite clear.

cheers,

-matt