Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

gh-136879: Make os.spawn* arg signatures consistent with os.exec*#144458

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.

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

Already on GitHub?Sign in to your account

Closed

Conversation

@kovan
Copy link
Contributor

@kovankovan commentedFeb 3, 2026
edited by github-actionsbot
Loading

Summary

  • Updatesos.spawnl,spawnle,spawnlp, andspawnlpe function signatures to showarg0, arg1, ... explicitly
  • This matches the documentation style of theos.execl family of functions

Before:spawnl(mode, path, ...)
After:spawnl(mode, path, arg0, arg1, ...)

Source verification

  • Verified inLib/os.py that both exec* and spawn* use*args parameter

Test plan

  • make check passed

🤖 Generated withClaude Code


📚 Documentation preview 📚:https://cpython-previews--144458.org.readthedocs.build/

Update os.spawnl, spawnle, spawnlp, and spawnlpe function signaturesto show arg0, arg1, ... explicitly, matching the os.execl family offunctions for consistency.Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Copy link
Member

@picnixzpicnixz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Strictly speaking, this isnot the signature at runtime. At runtime, the signature isspawnl(mode, path, *args) so the... part is correct. So I think we should first decide on the issue how we want to document the expanded args. Do we want to explicitly documentspawnl(mode, path, arg0, arg1, ...), orspawnl(mode, path, arg0, ...) or simply specify thatargs must be non-empty with args[0] being the program name by convention? since we did not discuss yet about it, I am closing the PR otherwise it will be kept open for too long.

@bedevere-app
Copy link

A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated.

Once you have made the requested changes, please leave a comment on this pull request containing the phraseI have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request.

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

Reviewers

@picnixzpicnixzpicnixz requested changes

Assignees

No one assigned

Labels

awaiting changesdocsDocumentation in the Doc dirskip news

Projects

Status: Todo

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@kovan@picnixz

[8]ページ先頭

©2009-2026 Movatter.jp