PEP 750: collect spec fixes discovered during final implementation work #4364
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PEP 123: Summary of changes
)Hate to do this < 24 hours after acceptance, but as we've been going through the spec with a fine-tooth comb, @lysnikolaou and I discovered a minor spec issue in PEP 750.
The intent of the debug specifier behavior is to precisely match the behavior of current day f-strings. The PEP as accepted got one detail wrong, fixed here.
(The wrong detail: if a debug specifier is used with a format spec but no conversion —
t"{value=:foo}"
— theInterpolation.conversion
should default toNone
, nots
as in the accepted PEP. Havings
as the default would be a departure from what f-strings do: they provide no default when there's aformat_spec
so that__format__()
is called.)📚 Documentation preview 📚: https://pep-previews--4364.org.readthedocs.build/