Issue 46772: Statically Initialize PyArg_Parser in clinic.py

➜

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.

This issue has been migrated to GitHub: https://github.com/python/cpython/issues/90928

classification

Title:	Statically Initialize PyArg_Parser in clinic.py
Type:		Stage:	needs patch
Components:	Interpreter Core	Versions:	Python 3.11

process

Status:	open	Resolution:
Dependencies:	46753 46773	Superseder:
Assigned To:	eric.snow	Nosy List:	eric.snow
Priority:	normal	Keywords:

Created on 2022-02-16 18:32 by eric.snow, last changed 2022-04-11 14:59 by admin.

Messages (1)
msg413351 - (view)	Author: Eric Snow (eric.snow) *	Date: 2022-02-16 18:32
The code generated by clinic.py is already partially statically initialized. Currently we init the other fields in Python/getargs.c:parser_init(), which runs the first time we try to use each parser. AFAICS, that remaining init that could be done statically using the data we have available in clinic.py during code generation. My primary interest is in static init of PyArg_Parser.kwtuple, which is a tuple containing only strings.

msg413351 - (view)

Author: Eric Snow (eric.snow) * (Python committer)

Date: 2022-02-16 18:32

The code generated by clinic.py is already partially statically initialized.  Currently we init the other fields in Python/getargs.c:parser_init(), which runs the first time we try to use each parser.  AFAICS, that remaining init that could be done statically using the data we have available in clinic.py during code generation.

My primary interest is in static init of PyArg_Parser.kwtuple, which is a tuple containing only strings.

History
Date	User	Action	Args
2022-04-11 14:59:56	admin	set	github: 90928
2022-02-16 18:36:54	eric.snow	set	dependencies: + Statically allocate and initialize the empty tuple., Add a Private API for Looking Up Global Objects
2022-02-16 18:32:25	eric.snow	create