Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 24 additions & 0 deletions Doc/reference/lexical_analysis.rst
Original file line number Diff line number Diff line change
Expand Up @@ -758,6 +758,30 @@ include expressions.
>>> foo.__doc__ is None
True

F-strings can also help with "printf-style" debugging.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this needs to at least describe the feature. See my 2 points in bpo-41045 for what I think needs to be included.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @rishi93,

Would you consider adding that this is new from version 3.8?


::

>>> foo = "bar"
>>> print(f"{foo=}")
"foo='bar'"
>>> print(f"{foo = }") # preserves whitespace before and after equals sign
"foo = 'bar'"

Optional format specifiers can be placed after the equals sign.
If no format specifiers are used then :meth:`repr` is used on the expression.
If format specifier (like :20) is given, then :meth:`str` is used on the
expression. You can use the repr() with the !r format specifier

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @rishi93,

I think !r is a conversion not a format specifier.

::

>>> line = "The mill's closed"
>>> f"{line = }"
'line = "The mill\'s closed"'
>>> f"{line = :20}"
"line = The mill's closed "
>>> f"{line = !r:20}"
'line = "The mill\'s closed" '

See also :pep:`498` for the proposal that added formatted string literals,
and :meth:`str.format`, which uses a related format string mechanism.

Expand Down