On Thursday, May 7, 2020 at 1:42:24 PM UTC-5, vitalije wrote: First of all I must say that testing with hypothesis is really great way to > discover hidden bugs. >
I am going to start by studying hypothesis. It looks like a great idea. I'll defer further work on unit testing until I see what you have done. The only work I have done so far is to change the `if __name__ == "__main__" code. I created a new "main" function. This function adds one feature: if the file name is "test" it calls unittest.main(). I assume this will be useful to you. If not, feel free to delete it. *Now the question of executing scripts* > > How should we re-synchronize tree widget with the possible changes in the > outline made by user script? The more I think about this problem, the more > I am sure that my initial plan of using diff algorithm won't work. > I don't have an opinion about what might work. However, if the tree-refresh branch is still relevant, I would like to see it merged into the mvc-prototype branch. That will make for me (and others) to study the latest code. I can't speak for everyone else but I would gladly accept this delay on > each executeScript command and in return have an insurance that no error in > my script will destroy my outline irrecoverably. I would like to be sure > that in case of an error in script I still can undo the whole operation and > return to the previous state. I know for certain that on more than one > occasion I've missed this undo ability very much. > A few added milliseconds is a trivial price to pay for safety. Go for it. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/2b216815-979c-4d5e-aa45-3b8f7593f9b6%40googlegroups.com.
