PEP 832: Update the Post-History and fix the formatting of the Change History (#4936)

Author: brettcannon

peps/pep-0832.rst

@@ -7,6 +7,7 @@ Type: Standards Track
 Created: 19-Jan-2026
 Python-Version: 3.15
 Post-History: `15-Apr-2026 <https://discuss.python.org/t/106998>`__
+              `23-Apr-2026 <https://discuss.python.org/t/106998/52>`__
 
 
 Abstract
@@ -346,7 +347,7 @@ in the file could record other virtual environments that the project has.
 Optionally, the path could be separated from a labelled name by a ``\t``. The
 default virtual environment would be allowed to be listed in the labelled
 section if an explicit label was desired. Another option would to record such
-data in a JSON trailer in the file.
+data in a JSON/JSONL trailer in the file.
 
 
 Acknowledgements
@@ -361,17 +362,19 @@ this PEP.
 Change History
 ==============
 
-- 23-Apr-2026: Add PyCharm and library-skills support; have redirect files
-               read up to the first newline; clarify there is no opinion to
-               having multiple virtual environments; explicitly use the
-               code editor example for the motivation; have
-               ``venv.executable()`` be configurable for the virtual
-               environment name; clarify symlinks are not to be treated in any
-               special way; move the Rationale after the Specification and
-               simplify the latter by moving details to the former; loosened
-               things involving "MAY", "SHOULD", and "NOT" so tools are not
-               required to do anything beyond how they interpret a redirect
-               file.
+- 23-Apr-2026
+
+  - Add PyCharm and library-skills support
+  - Have redirect files read up to the first newline
+  - Clarify there is no opinion to having multiple virtual environments
+  - Explicitly use the code editor example for the motivation
+  - Have ``venv.executable()`` be configurable for the virtual environment
+    name
+  - Clarify symlinks are not to be treated in any special way
+  - Move the Rationale after the Specification and simplify the latter by
+    moving details to the former
+  - Loosened things involving "MAY", "SHOULD", and "NOT" so tools are not
+    required to do anything beyond how they interpret a redirect file
 
 
 Copyright