# PEP750: Template Strings (new updates)

**URL:** <https://discuss.python.org/t/pep750-template-strings-new-updates/71594>\
**Category:** PEPs\
**Created:** [November 18, 2024, 5:44pm UTC](https://discuss.python.org/t/pep750-template-strings-new-updates/71594 "2024-11-18T17:44:56Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![steve.dower](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/steve.dower/32/56_2.png) [@steve.dower](https://discuss.python.org/u/steve.dower)\
**Post date:** [November 18, 2024, 10:56pm UTC](https://discuss.python.org/t/pep750-template-strings-new-updates/71594/5 "2024-11-18T22:56:15Z")

</div>

> [@effigies](#):
>
> This restriction does not apply to a template, since it is the function the template is passed to that needs to decide what to do with it. I’m assuming that you don’t want to complicate this PEP by actually defining a `Template[bytes]`, but it would be nice to see this explicitly declared out-of-scope or in Rejected Ideas (and my preference would be out-of-scope, since it seems like a natural extension in the future).

I would gladly take a `struct.pack(tb"{x:<I}{y:<h}")` whenever 🙂

---

_[View the full topic](https://discuss.python.org/t/pep750-template-strings-new-updates/71594)._