On Sun, Sep 8, 2019 at 2:52 PM Matt Wilkie <map...@gmail.com> wrote:
> Thank you for reporting on the variety in the to-be or not-to-be f-string landscape. This side by side comparison useful. You're welcome. I have only been using f-strings in my present work on orange. String concatenations are perfect for comparisons. Examples: # Example 1: raise self.AstNotEqual( f"node1: {node1}\n" f"node2: {node2}") # Example 2: g.trace("COMPARE LIST ITEMS") print( f"list1: {node1}\n" f"list2: {node2}") The print statement in the second example preserves alignments. Using just g.trace would not work as well. My present plan is to merge the fstring branch into devel in a day or two. I'll feel free to revert to % strings where they seem clearer. 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/c3f6e868-2396-4136-9627-e532192b5e2b%40googlegroups.com.