Skip to content

Clarify run_process Ctrl+C documentation - #3486

Open
Madhur-7568 wants to merge 1 commit into
python-trio:mainfrom
Madhur-7568:docs-3300-run-process-ctrlc
Open

Madhur-7568 wants to merge 1 commit into
python-trio:mainfrom
Madhur-7568:docs-3300-run-process-ctrlc

Conversation

@Madhur-7568

Copy link
Copy Markdown
Contributor

Summary

Clarify the run_process documentation around Ctrl+C behavior.

The note now explains that child processes normally receive Ctrl+C along with the parent process. It also points readers to Python's process_group and start_new_session options for cases where different behavior is needed.

Closes #3300

@A5rocks A5rocks added skip newsfragment Newsfragment is not required docs labels Aug 3, 2026
@Madhur-7568

Copy link
Copy Markdown
Contributor Author

Hi, I just wanted to check if you have any feedback or suggestions for this pr.

@A5rocks

A5rocks commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

Thanks! To be honest, since I don't really know how the issue should be fixed, I think this is fine. But I have some quibbles about wording: I actually preferred the old wording! However, I think mentioning the relevant args is a good idea. Sorry about the delay xd

@arian-bozorgzad

Copy link
Copy Markdown

Thanks! To be honest, since I don't really know how the issue should be fixed, I think this is fine. But I have some quibbles about wording: I actually preferred the old wording! However, I think mentioning the relevant args is a good idea. Sorry about the delay xd

Hi,

I recently opened PR #3512 in Trio to expose AsyncIOWrapper publicly and add the related typing tests and documentation.

I’m still fairly new to contributing to larger open-source projects, so I wanted to reach out and ask if you would be willing to take a look when you have some time. I’d especially appreciate any feedback on the API/export approach or anything you think should be changed before it’s ready and if not merged tell me why so i can learn from it .

PR: #3512

There’s currently one failing macOS 3.15-dev CI job, but from the logs it looks like the Python setup failed because of a GitHub/DNS issue before the tests actually ran. The other checks were completed successfully.

No rush at all , I mainly wanted to make sure the PR reaches someone familiar with the project.
Thank you for maintaining this project

Thanks for your time,
Arian

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs skip newsfragment Newsfragment is not required

Projects

None yet

Development

Successfully merging this pull request may close these issues.

run_process: Document pitfalls re/ Ctrl+C and not creating a new process group

3 participants