While I like them, their only benefit is reducing a call of "string with idens".format(explicits_for_idens) to f"string with explicits for idens", it's syntactic sugar that saves you ".", "ormat", and the parenthesis, nothing more. And it introduces backwards incompatible in minor version numbers, which it really shouldnt.
it's syntactic sugar that saves you ".", "ormat", and the parenthesis, nothing more
I disagree. The greatest benefit of f-strings is that the save you the need to zip the values in your head. Consider this:
'a={} x={} u={} z={} y={}'.format(a, x, u, y, z)
You need to make sure that the list of {}s matches the format arguments. Compare to this:
f'a={a} x={x} u={u} z={y} y={z}'
Now that each expression is written in the place it is supposed to be formatted, we can clearly see that I've "accidentally" mixed y and z. The same mistake exists in the .format() version, but much harder to notice.
4
u/13steinj Jun 28 '18
Types aren't beneficial to every developer. Asyncio has severe usability issues, I'd rather use gevent in an async manner.