On Sat, Jan 11, 2020 at 2:11 PM Brian Theado <brian.the...@gmail.com> wrote:
> I have doubts about the following entries you are suppressing: assert, except, raise. Imo, they are fine. Assert signal that something is seriously wrong with the tool, not the user input. In addition to providing coverage data, pytest is actually running the unit tests. If an assert fails we can deal the failure. Suppressing the coverage tests is not a problem. The new silent-fstringify-files command suppresses most output, ensuring any serious failures will be obvious. This command now fstringifies all of Leo's core files without serious messages, including failed asserts. 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 leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS0waGxn%3DNiNGxy-RDH3hQ%2BPtfzJw3aVDQoZb8zdEtEazw%40mail.gmail.com.
