On Mar 25, 5:17 pm, "Edward K. Ream" <[email protected]> wrote: > People want all of Leo's advantages without Leo.
Actually, I have one more problem that is similar. I also want to do something using leo and @test nodes, something that I can do without using leo and writing unit tests using unittest directly. But I want to use leo because I like it. Ok, everything above is very obscure. Here are the facts: My goal is to run pylint against the content of @test nodes. Usually I have a @thin file called test.py and all @test nodes are stored in that file. Now, if I run pylint against that file, it complains. Here is an example: E0602: 10: Undefined variable 'self' I'm not quoting the context here, because I think I will be able to explain the problem without it. Here 'self' is that 'self' that was added to leo's unit testing framework, that one I've mentioned above. This 'self' makes sense when the code inside @test nodes is being run by leo. But it confuses pylint when I'm running it against the derived file. Any hints? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
