Issue on page /notebooks/05-Python_I.html

[kokestu]

Since Python 3, we've had really nice format strings that don't require overloading of the % operator. I think these should be preferred, e.g.:

"%d is Even!" % x

can be

f"{x} is Even!"

[davidorme]

They're generally more compact and easier to read too. Basically, 'str'.format() without having to type the .format(). The only real pain is when
they wrap over multiple lines and you have to remember to add f" to all lines.

[mhasoba]

Yes, this is an old issue: #22

Definitely on top of the list for fixes this year!

[fwimp]

As in #22 Totally on board with this, and glad for the reminder.

They're generally more compact and easier to read too. Basically, 'str'.format() without having to type the .format(). The only real pain is when they wrap over multiple lines and you have to remember to add f" to all lines.

Only other advantage I see to string.format() over f strings (though I have been including them both in my teaching of CMEE this year) is that it sticks more clearly to the object.method() paradigm that one tends to work with in python.

That said, the way we specify some sorts of literals (u-strings, r-strings and bytes literals) make formatted strings specified in the f"string" method more sensical. Though most CMEE students will be unlikely to come across these types of string literals day-to-day.

As an aside, I wonder whether calling the format method of a string in 3.6 onwards returns a formatted string literal, or just a formatted string literal...

[fwimp]

FINE, this will be one of my big projects for this year. I'll start on it now.

[davidorme]

I've recently come across this detail on not using f strings in logging:

https://blog.pilosus.org/posts/2020/01/24/python-f-strings-in-logging/

Well accepted enough that pylint warns about it.

[fwimp]

Ahh interesting and good to know about, thank you! For CMEEs it likely is not the most important that they know that (as honestly I can count on one hand the number in the last 5 years that actually implemented logging into any of their code) but I might look to incorporate a warning on it into the logging_in_python notebook included in PR #77 .

[fwimp]

@davidorme Added message in 9f907c