Repository navigation
gh-83714: Use statx on Linux 4.11 and later in os.stat #136334
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
Closed
Closed
Changes from 1 commit
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
99c9efd
bpo-39533: Use statx on Linux 4.11 and later in os.stat
jbosboom cebd5b7
Fix versionadded documentation syntax
jbosboom ffd7a89
Add blurb
jbosboom d53650a
Fix typo stx_subvol -> st_subvol in docs
jbosboom 4e4e917
Allow statx to be explicitly configured out for old glibc
jbosboom bc3155b
Implement os.statx
jbosboom b0e8276
Use correct function name in os.statx argument validation errors
jbosboom 1a8a6d6
Merge branch 'main' into statx
jbosboom f71315e
Move statx-specific members from os.stat_result to new os.statx_result
jbosboom 1f1e959
make regen-configure
jbosboom 7440397
Reimplement os.statx_result using PyMemberDef and PyGetSetDef; remove…
jbosboom 534e33f
Remove statx-specific members from os.stat_result documentation
jbosboom 7dc75d0
Simplify statx configure check
jbosboom 894efb5
Document os.statx
jbosboom d5bc601
Prepare for review
jbosboom 5b36cf0
Document st_birthtime fallback behavior
jbosboom 6be85a3
Implement os.stat with statx only if the statx syscall works
jbosboom c32ee72
Test statx PathLike and dir_fd handling
jbosboom c84f783
statx docs fixes
jbosboom File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Document st_birthtime fallback behavior
- Loading branch information
commit 5b36cf0e6d93126cb25c7689c9a2513d2a463a81
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be able to make the missing c func / struct pieces stop erroring by adding to:
cpython/Doc/conf.py
Line 121 in 4e00e25
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will also work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Running
make htmlandmake checkas directed by the devguide, I don't see any warnings.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Getting all the warnings out of the docs build is difficult (there are many warnings in non-changed code which don't matter for PRs; but new ones do); the CI does check for new warnings and attaches them to PRs. I can see some here on the Github UI: