8000 PEP 768: Make sure C API names start with `Py_` (GH-4473) · python/peps@83ccbaa · GitHub
[go: up one dir, main page]

Skip to content

Commit 83ccbaa

Browse files
authored
PEP 768: Make sure C API names start with Py_ (GH-4473)
- Remove the struct tag - Add `Py_` to `MAX_SCRIPT_PATH_SIZE` As discussed in: https://discuss.python.org/t/73969/58
1 parent 65602dc commit 83ccbaa

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

peps/pep-0768.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -135,9 +135,9 @@ A new structure is added to PyThreadState to support remote debugging:
135135

136136
.. code-block:: C
137137
138-
typedef struct _remote_debugger_support {
138+
typedef struct {
139139
int debugger_pending_call;
140-
char debugger_script_path[MAX_SCRIPT_PATH_SIZE];
140+
char debugger_script_path[Py_MAX_SCRIPT_PATH_SIZE];
141141
} _PyRemoteDebuggerSupport;
142142
143143
This structure is appended to ``PyThreadState``, adding only a few fields that
@@ -147,7 +147,7 @@ provides a filesystem path to a Python source file (.py) that will be executed w
147147
the interpreter reaches a safe point. The path must point to a Python source file,
148148
not compiled Python code (.pyc) or any other format.
149149

150-
The value for ``MAX_SCRIPT_PATH_SIZE`` will be a trade-off between binary size
150+
The value for ``Py_MAX_SCRIPT_PATH_SIZE`` will be a trade-off between binary size
151151
and how big debugging scripts' paths can be. To limit the memory overhead per
152152
thread we will be limiting this to 512 bytes. This size will also be provided as
153153
part of the debugger support structure so debuggers know how much they can

0 commit comments

Comments
 (0)
0