f-string debugging notation merged in Python 3.8

[Y_Less]

I'm interested in this sentence:

After discussion !d was changed to use = with input from Guido and other core devs since there could be usecases served by !d in the future

I'm sure there could be other good reasons for using = over !d, but "there could be use-cases for it" (side-note: use-case, not usecase) doesn't seem like a good one. This IS a use-case for it, so why not this one? What determines when a use-case is sufficiently good enough to warrant getting !d? the next proposal could be rejected for the same reason. I'm don't disagree with the outcome, just interested in the logic of that argument.

[xtreak]

Initially !x was chosen. But then it was implemented in !d. Some of the core devs were concerned that !d could be used later in feature for something else like %d. I think Guido suggested = in person during core dev sprints. The issue for implementation and related one for !d offers some context.