It has the advantage of being able to put variables after instead of having to do it at the time that the string is created. As an example, if I want to print a format for a list (to make it look like a table), I can re-use a .format() string like so: table_fmt = "name: {:8} age: {:8} weight: {:3}" items_1 = ("John", 35, 180) items_2 = ("Susan", 35, 130) print(table_fmt.format(*items_1)) print(table_fmt.format(*items_2)) Or if I want to print in a different order, I can also do something like: order = ("Pizza", 25.00, "Visa", "ACCEPTED") fmt = "status: {3}, item: {0}, cost: {1}, payment method: {2}" print(fmt.format(*order)) You can also put in a function result in a .format() string without it breaking the readability, while the same isn't true for f-strings: value = 20.0 def price_after_taxes(cost): return cost * 1.05 print("After taxes, you have to pay {} for your pizza".format(price_after_taxes(cost))) So it is useful in some cases, although f strings usually are a lot faster and nicer to read. It's a tradeoff between readability and flexibility. More on reddit.com

This post was triggered by a discussion between @ideasman42 and myself in D8072: API docs: intro overhaul. To provide some context to this post: Python has three different approaches for string formatting: printf-sty… More on devtalk.blender.org

it's not that hard to follow the formatting help under the text field (using tab doesn't work like in text editor for browser input field). the harder part is probably doing it in one try (like what i experiencing just now)

text
enter
....<code>
........<indented code>
........<indented too>
............<inside indented>
....</code>
enter

More on reddit.com

Nearly every people I know use black. More on reddit.com