classification
Title: Make C-API docs clear about what the "main" interpreter is
Type: Stage: patch review
Components: Documentation Versions: Python 3.8
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: nanjekyejoannah Nosy List: eric.snow, nanjekyejoannah, ncoghlan
Priority: normal Keywords: patch

Created on 2019-03-30 15:55 by nanjekyejoannah, last changed 2019-04-05 17:32 by nanjekyejoannah.

Pull Requests
URL Status Linked Edit
PR 12666 open nanjekyejoannah, 2019-04-02 19:21
Messages (3)
msg339207 - (view) Author: Joannah Nanjekye (nanjekyejoannah) * (Python triager) Date: 2019-03-30 15:55
Following up a discussion on a PR here : https://github.com/python/cpython/pull/12238, There is need to make sure the C-API docs are clear about what the "main" interpreter is.
msg339508 - (view) Author: Eric Snow (eric.snow) * (Python committer) Date: 2019-04-05 17:27
I should have added something like this earlier, but here are key points to consider covering:

* "main" interpreter is the original, created when the runtime initializes
* historically almost always the only Python interpreter in a process
    * this is changing (more projects using subinterpreters, PEP 554)
    * in the "python" executable, subinterpreters available via extension modules (but uncommon)
* it has extra responsiblities:
    * signal handling, in main thread
    * "pending calls", in main thread
        * not necessarily something to publicize :)
    * running in the "main" thread
        * can be taken over by a sub-interpreter, but not likely
    * execution *during* runtime initialization
    * usually (always?) the active interpreter during runtime finalization
    * others?
* no strong link between interpreters (e.g. main <--> sub <--> sub)
    * no record of what interpreter was active (if any) when a subinterpreter was created
    * no "parent" interpreter
    * thread states may share thread ID
* a bunch of stuff in the C-API and in the runtime still assumes that the main interpreter is running in the current OS thread
* other stuff?


Not all of that necessarily belongs there in the docs, but a lot of it does. :)
msg339509 - (view) Author: Joannah Nanjekye (nanjekyejoannah) * (Python triager) Date: 2019-04-05 17:32
Thanks for this feedback. Let me see how I can incorporate this in the PR.
History
Date User Action Args
2019-04-05 17:32:06nanjekyejoannahsetmessages: + msg339509
2019-04-05 17:27:11eric.snowsetnosy: + ncoghlan
messages: + msg339508
2019-04-02 19:21:06nanjekyejoannahsetkeywords: + patch
stage: patch review
pull_requests: + pull_request12594
2019-04-02 18:20:43nanjekyejoannahsetcomponents: + Documentation
versions: + Python 3.8
2019-04-01 15:07:56eric.snowsetnosy: + eric.snow
2019-03-30 15:56:18nanjekyejoannahsetassignee: nanjekyejoannah
2019-03-30 15:55:50nanjekyejoannahcreate