[JSap0914]

Description

normalize_string_prefix is documented to "make all string prefixes lowercase", and it already normalises F→f and B→b. However, when t-string support was added in #4805 the T→t normalisation was accidentally omitted.

Bug: Black leaves T"..." unchanged instead of normalising it to t"...":

# Before (Black ≥ 26.5 with --target-version py314)
T"hello"   →   T"hello"   # wrong — should be t"hello"
RT"hello"  →   RT"hello"  # wrong — should be Rt"hello"
rT"hello"  →   rT"hello"  # wrong — should be rt"hello"

Fix: Add a single .replace("T", "t") step to the existing chain in normalize_string_prefix.

Verification:

$ pytest tests/test_format.py -k pep_750 -v
PASSED  tests/test_format.py::test_simple_format[pep_750]

AI-assisted: this PR was prepared with the help of an AI coding tool.

Checklist - did you ...

• Implement any code style changes under the --preview style, following the stability policy?
• Add an entry in CHANGES.md if necessary?
• Add / update tests if necessary?
• Add new / update outdated documentation?

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[JSap0914]

T→t prefix normalization is now gated behind Preview.normalize_tstring_prefix, so it only applies in --preview mode as requested.

[cobaltt7]

Can you inline the Preview.normalize_tstring_prefix in mode call instead of making a utility function?

[cobaltt7]

I'd prefer for mode to be required, just so we don't accidentally forget it anywhere. Black's public API isn't considered stable, so it's not a breaking change.

[github-actions]

diff-shades results comparing this PR (8ea4c12) to main (b74b230):

--preview style: no changes

--stable style: no changes

---

What is this? | Workflow run | diff-shades documentation

[JelleZijlstra]

Do we need this inline import? Why can't we just import black.mode normally?

[cobaltt7]

@JSap0914 are you still updating this?

[cobaltt7]

Closing as stale. Feel free to open a new PR following the guidelines I set above. I'll also create a new issue for this so it may be picked up by someone else instead.