This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: [subinterpreters] Confusing docs about state after calling Py_NewInterpreter()
Type: Stage:
Components: Subinterpreters Versions:
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: eric.snow, nanjekyejoannah
Priority: normal Keywords:

Created on 2019-08-19 19:05 by nanjekyejoannah, last changed 2022-04-11 14:59 by admin.

Messages (1)
msg349964 - (view) Author: Joannah Nanjekye (nanjekyejoannah) * (Python committer) Date: 2019-08-19 19:05
In the documentation for Py_NewInterpreter(): It is said that :

The return value points to the first thread state created in the new sub-interpreter.  This thread state is made in the current thread state.

I think changing :

This thread state is made in the current thread state.

To:

This thread state is made the current thread state.

Sounds good. Since a call such as:

substate = Py_NewInterpreter()

makes *substate* the current state. no?

The *in* takes me in a different direction of thought.
History
Date User Action Args
2022-04-11 14:59:19adminsetgithub: 82069
2020-05-15 00:53:42vstinnersetcomponents: + Subinterpreters
title: Sub-interpreters : Confusing docs about state after calling Py_NewInterpreter() -> [subinterpreters] Confusing docs about state after calling Py_NewInterpreter()
2019-09-11 13:42:21eric.snowsetnosy: + eric.snow
2019-08-19 19:05:22nanjekyejoannahcreate