Skip to content

Commit 0c8df5f

Browse files
Some extra additions
1 parent 1073f43 commit 0c8df5f

1 file changed

Lines changed: 9 additions & 9 deletions

File tree

peps/pep-0788.rst

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,6 @@ proposal.
7171
Motivation
7272
==========
7373

74-
7574
Foreign threads hang during interpreter finalization
7675
----------------------------------------------------
7776

@@ -153,7 +152,7 @@ Specification
153152
PEP was indeed approved. Following discussion with Python's Steering Council, the
154153
author of this PEP believed the right course of action was to deviate from
155154
some of the working group's recommendations in order to produce the best possible
156-
design.
155+
design while also avoiding invasive changes to Python's ecosystem.
157156

158157

159158
Interpreter guards
@@ -255,7 +254,7 @@ Interpreter views
255254
attached thread state.
256255
257256
258-
.. c:function:: PyInterpreterView *PyUnstable_InterpreterView_FromMain()
257+
.. c:function:: PyInterpreterView *PyInterpreterView_FromMain()
259258
260259
Create a view for the "main" interpreter.
261260
@@ -467,9 +466,10 @@ The following APIs from this PEP are to be added to the limited C API:
467466
4. :c:type:`PyInterpreterView` (as an opaque structure)
468467
5. :c:func:`PyInterpreterView_FromCurrent`
469468
6. :c:func:`PyInterpreterView_Close`
470-
7. :c:type:`PyInterpreterGuard` (as an opaque structure)
471-
8. :c:func:`PyInterpreterGuard_FromCurrent`
472-
9. :c:func:`PyInterpreterGuard_Close`
469+
7. :c:func:`PyInterpreterView_FromMain`
470+
8. :c:type:`PyInterpreterGuard` (as an opaque structure)
471+
9. :c:func:`PyInterpreterGuard_FromCurrent`
472+
10. :c:func:`PyInterpreterGuard_Close`
473473
474474
475475
Rationale
@@ -551,7 +551,8 @@ This PEP specifies no breaking changes.
551551
552552
Existing code **does not** have to be rewritten to use the new APIs from
553553
this PEP, and all ``PyGILState`` APIs will continue to work. Use of ``PyGILState``
554-
APIs will not emit any form of warning during compilation or at runtime.
554+
APIs will not emit any form of warning during compilation or at runtime. The APIs
555+
will merely not be developed further.
555556
556557
557558
Security Implications
@@ -572,7 +573,6 @@ to the new APIs.
572573
Examples
573574
--------
574575
575-
576576
Example: A library interface
577577
****************************
578578
@@ -976,7 +976,7 @@ Acknowledgements
976976
This PEP is based on prior work, feedback, and discussions from many people,
977977
including Victor Stinner, Antoine Pitrou, David Woods, Sam Gross, Matt Page,
978978
Ronald Oussoren, Matt Wozniski, Eric Snow, Steve Dower, Petr Viktorin,
979-
Gregory P. Smith, Alyssa Coghlan, and Python's Steering Council.
979+
Gregory P. Smith, Alyssa Coghlan, and Python's 2026 Steering Council.
980980

981981

982982
Copyright

0 commit comments

Comments
 (0)