Doc/library/os.rst: os.waitid absent on MacOS#104558
Conversation
Sorry, something went wrong.
b2399e2 to
e7bc73d
Compare
May 16, 2023 18:11
I probably should have supported the statement that it's disabled, sorry. Lines 9191 to 9213 in c649df6 |
Sorry, something went wrong.
|
The more interesting question here is why There's some discussion in #55021, |
Sorry, something went wrong.
You know…no it's not! If it takes 6 months to get a doc fix in and 12 months to have a policy debate and maybe change the policy and get a code fix in, I am entirely uninterested in postponing the former in favor of the latter. Open a new PR or Issue to expose Thank you. I am not as bitter as I sound. |
Sorry, something went wrong.
I don't know about other core devs, but personally I only regularly check GitHub issues for things to work on. That's mostly out of habit, but we do have a longstanding culture of having issues for almost all changes. I'm not going to argue that's a good thing, but it does explain why PRs without an issue can get lost and not get core dev attention. Anyway, I'll file an issue about exposing |
Sorry, something went wrong.
Co-authored-by: AN Long <aisk@users.noreply.github.com>
ronaldoussoren
left a comment
There was a problem hiding this comment.
LGTM
Thanks for the PR!
Sorry, something went wrong.
|
Thanks @johnhawkinson for the PR, and @ronaldoussoren for merging it 🌮🎉.. I'm working now to backport this PR to: 3.11, 3.12. |
Sorry, something went wrong.
* Doc/library/os.rst: `os.waitid` absent on MacOS (cherry picked from commit db1c882) Co-authored-by: John Hawkinson <jhawk@alum.mit.edu> Co-authored-by: AN Long <aisk@users.noreply.github.com>
* Doc/library/os.rst: `os.waitid` absent on MacOS Co-authored-by: AN Long <aisk@users.noreply.github.com>
* Doc/library/os.rst: `os.waitid` absent on MacOS Co-authored-by: AN Long <aisk@users.noreply.github.com>
* Doc/library/os.rst: `os.waitid` absent on MacOS Co-authored-by: AN Long <aisk@users.noreply.github.com>
os.waitid()is disabled on MacOS, and that's not documented.It's not precisely clear why its disabled, and it was discussed in #55021 (deeplink) which was closed without resolution.
But regardless of why, the documentation needs to clearly reflect that the function is not available.
I've followed the model of
os.fdatasync()and noted the lack of availability in theNotesection, rather than theAvailabilitysection. Absent that precedent, I would have instead changedAvailabilitytoUnix, not Emscripten, not Macos, not WASI, perhaps somewhat consistent withCLOCK_UPTIME_RAWin time.rst L866.I hope this is appropriate for a PR without an Issue, but if I'm wrong, I apologize and am happy to file an Issue.
📚 Documentation preview 📚: https://cpython-previews--104558.org.readthedocs.build/