Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

drop fork and always use the posix_spawn family of functions #12073

Open
glyph opened this issue Jan 3, 2024 · 0 comments
Open

drop fork and always use the posix_spawn family of functions #12073

glyph opened this issue Jan 3, 2024 · 0 comments

Comments

@glyph
Copy link
Member

glyph commented Jan 3, 2024

As mentioned on #12071 , os.fork is now throwing a deprecation warning.

Better than falling back to os.fork for features that are not yet supported by posix_spawn would be falling back to an executable stub that can perform all the post-exec work.

The reason we don't do this right now is that we don't want to pay the exec-Python penalty twice, but a minimal Rust stub could mitigate this significantly; we would still have only one call to posix_spawn, the executable in question would do its minimal bootstrap work, then exec.

We don't need to worry about adding a new hard binary dependency here either, because the slow Python-only fallback here would also be extremely short.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant