Skip to content

PEP 768: Remove Py_MAX_SCRIPT_PATH_SIZE #4591

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 16, 2025
Merged

PEP 768: Remove Py_MAX_SCRIPT_PATH_SIZE #4591

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions peps/pep-0768.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -137,7 +137,7 @@ A new structure is added to PyThreadState to support remote debugging:

typedef struct {
int debugger_pending_call;
char debugger_script_path[Py_MAX_SCRIPT_PATH_SIZE];
char debugger_script_path[...];
} _PyRemoteDebuggerSupport;

This structure is appended to ``PyThreadState``, adding only a few fields that
Expand All @@ -147,7 +147,7 @@ provides a filesystem path to a Python source file (.py) that will be executed w
the interpreter reaches a safe point. The path must point to a Python source file,
not compiled Python code (.pyc) or any other format.

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