Specify module location as string.templatelib

Author: davepeck

peps/pep-0750.rst

@@ -109,13 +109,13 @@ Template String Literals
 
 This PEP introduces a new string prefix, ``t``, to define template string literals.
 These literals resolve to a new type, ``Template``, found in the standard library
-module ``<<TBD>>``.
+module ``string.templatelib``.
 
 The following code creates a ``Template`` instance:
 
 .. code-block:: python
 
-    from TBD import Template
+    from string.templatelib import Template
     template = t"This is a template string."
     assert isinstance(template, Template)
 
@@ -134,7 +134,8 @@ see the `Raw Template Strings`_ section below for more information.
 The ``Template`` Type
 ---------------------
 
-Template strings evaluate to an instance of a new immutable type, ``<<TBD>>.Template``:
+Template strings evaluate to an instance of a new immutable type, 
+``string.templatelib.Template``:
 
 .. code-block:: python
 
@@ -192,7 +193,7 @@ The ``Interpolation`` Type
 --------------------------
 
 The ``Interpolation`` type represents an expression inside a template string.
-Like ``Template``, it is a new class found in the ``<<TBD>>`` module:
+Like ``Template``, it is a new class found in the ``string.templatelib`` module:
 
 .. code-block:: python
 
@@ -315,7 +316,7 @@ interpolations in uppercase:
 
 .. code-block:: python
 
-    from TBD import Template, Interpolation
+    from string.templatelib import Template, Interpolation
 
     def lower_upper(template: Template) -> str:
         """Render static parts lowercased and interpolations uppercased."""
@@ -506,7 +507,7 @@ specifiers like ``:.2f``. The full code is fairly simple:
 
 .. code-block:: python
 
-    from TBD import Template, Interpolation
+    from string.templatelib import Template, Interpolation
 
     def convert(value: object, conv: Literal["a", "r", "s"] | None) -> object:
         if conv == "a":
@@ -579,7 +580,7 @@ We can implement an improved version of ``StructuredMessage`` using template str
 .. code-block:: python
 
     import json
-    from TBD import Interpolation, Template
+    from string.templatelib import Interpolation, Template
     from typing import Mapping
 
     class TemplateMessage:
@@ -636,7 +637,7 @@ and a ``ValuesFormatter`` for JSON output:
 
     import json
     from logging import Formatter, LogRecord
-    from TBD import Interpolation, Template
+    from string.templatelib import Interpolation, Template
     from typing import Any, Mapping
 
 
@@ -820,7 +821,7 @@ best practice for many template function implementations:
 
 .. code-block:: python
 
-    from TBD import Template, Interpolation
+    from string.templatelib import Template, Interpolation
 
     def process(template: Template) -> Any:
         for item in template:
@@ -1228,14 +1229,8 @@ The Final Home for ``Template`` and ``Interpolation``
 
 Previous versions of this PEP proposed placing the ``Template`` and
 ``Interpolation`` types in: ``types``, ``collections``, ``collections.abc``,
-and even in a new top-level module, ``templatelib``. As of this writing, no core
-team consensus has emerged on the final location for these types. The current
-PEP leaves this open for a final decision.
-
-One argument in favor of a new top-level ``templatelib`` module is that it would
-allow for future addition of related methods (like ``convert()``) and for
-potential future template processing code to be added to submodules
-(``templatelib.shell``, etc.).
+and even in a new top-level module, ``templatelib``. The final decision was to
+place them in ``string.templatelib``.
 
 
 Enable Full Reconstruction of Original Template Literal