GeezerVison

(Marking as ready so we get some eyes on this. I think there are a lot of directions we can take this content, including simply deciding not to include it in the Python docs whatsoever. Hopefully there's something useful here, though?)

I'll add this to my to-do list. I have a few reorganisation thoughts after a quick skim, but I want to look at things properly before doing so. Would you mind if I push directly to the branch? GH makes it hard to effectively suggest that kind of change.

A

Would you mind if I push directly to the branch?

Not at all; please do! The more eyes and authors the better here, I think.

Thanks @StanFromIreland -- that is all helpful feedback. Lots of work still to do here to massage this into something usable.

The proposed doc and its length makes me think that the t-string tutorial should not be in the python tutorial, but in another document. (See logging for example of doc split between tutorial, cookbook, reference)

A t-string HOWTO seems like a good idea.

I'll third that. t-strings, as introduced here, are useful if you're writing a library; it's not really about putting data in fancy messages.

I'm happy to close this and regroup on a future potential tutorial doc.