-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
gh-107959: clarify Unix-availability of os.lchmod()
#107960
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
Conversation
1bd9fff
to
dc0025a
Compare
Well... I guess that comes out when one has apparently no deep knowledge of rst syntax and was too lazy to install all build dependencies ^^ Any idea how one properly adds some comment to the availability? |
Ah that’s not how the directive is designed! The value must be Process detail: please don’t use force pushes for Python PRs, it makes it harder to see changes over time, and github creates notifications with non-working links for reviewers. PRs are always squash merged in the end so there is no need to rewrite history for a PR. See https://devguide.python.org/getting-started/pull-request-lifecycle/index.html |
POSIX specifies that implementations are not required to support changing the file mode of symbolic links, but may do so. Consequently, `lchmod()` is not part of POSIX (but mentioned for implementations which do support the above). The current wording of the availability of `os.lchmod()` is rather vague and improved to clearly tell which POSIX/Unix/BSD-like support the function in general (those that support changing the file mode of symbolic links). Further, some examples of major implementations are added. Data for the BSDs taken from their online manpages. Co-authored-by: Adam Turner <[email protected]> Signed-off-by: Christoph Anton Mitterer <[email protected]>
f3c2508
to
47a799c
Compare
Sorry for another force push... but that all became to messy to me and I had rebased my branch to The new single commit should include the suggested |
Thanks @calestyo for the PR, and @serhiy-storchaka for merging it 🌮🎉.. I'm working now to backport this PR to: 3.11, 3.12. |
GH-113066 is a backport of this pull request to the 3.12 branch. |
…-107960) POSIX specifies that implementations are not required to support changing the file mode of symbolic links, but may do so. Consequently, `lchmod()` is not part of POSIX (but mentioned for implementations which do support the above). The current wording of the availability of `os.lchmod()` is rather vague and improved to clearly tell which POSIX/Unix/BSD-like support the function in general (those that support changing the file mode of symbolic links). Further, some examples of major implementations are added. Data for the BSDs taken from their online manpages. (cherry picked from commit f14e3d5) Co-authored-by: Christoph Anton Mitterer <[email protected]> Signed-off-by: Christoph Anton Mitterer <[email protected]> Co-authored-by: Adam Turner <[email protected]>
…-107960) POSIX specifies that implementations are not required to support changing the file mode of symbolic links, but may do so. Consequently, `lchmod()` is not part of POSIX (but mentioned for implementations which do support the above). The current wording of the availability of `os.lchmod()` is rather vague and improved to clearly tell which POSIX/Unix/BSD-like support the function in general (those that support changing the file mode of symbolic links). Further, some examples of major implementations are added. Data for the BSDs taken from their online manpages. (cherry picked from commit f14e3d5) Co-authored-by: Christoph Anton Mitterer <[email protected]> Signed-off-by: Christoph Anton Mitterer <[email protected]> Co-authored-by: Adam Turner <[email protected]>
GH-113067 is a backport of this pull request to the 3.11 branch. |
…) (GH-113066) gh-107959: clarify Unix-availability of `os.lchmod()` (GH-107960) POSIX specifies that implementations are not required to support changing the file mode of symbolic links, but may do so. Consequently, `lchmod()` is not part of POSIX (but mentioned for implementations which do support the above). The current wording of the availability of `os.lchmod()` is rather vague and improved to clearly tell which POSIX/Unix/BSD-like support the function in general (those that support changing the file mode of symbolic links). Further, some examples of major implementations are added. Data for the BSDs taken from their online manpages. (cherry picked from commit f14e3d5) Signed-off-by: Christoph Anton Mitterer <[email protected]> Co-authored-by: Christoph Anton Mitterer <[email protected]> Co-authored-by: Adam Turner <[email protected]>
…) (GH-113067) gh-107959: clarify Unix-availability of `os.lchmod()` (GH-107960) POSIX specifies that implementations are not required to support changing the file mode of symbolic links, but may do so. Consequently, `lchmod()` is not part of POSIX (but mentioned for implementations which do support the above). The current wording of the availability of `os.lchmod()` is rather vague and improved to clearly tell which POSIX/Unix/BSD-like support the function in general (those that support changing the file mode of symbolic links). Further, some examples of major implementations are added. Data for the BSDs taken from their online manpages. (cherry picked from commit f14e3d5) Signed-off-by: Christoph Anton Mitterer <[email protected]> Co-authored-by: Christoph Anton Mitterer <[email protected]> Co-authored-by: Adam Turner <[email protected]>
…-107960) POSIX specifies that implementations are not required to support changing the file mode of symbolic links, but may do so. Consequently, `lchmod()` is not part of POSIX (but mentioned for implementations which do support the above). The current wording of the availability of `os.lchmod()` is rather vague and improved to clearly tell which POSIX/Unix/BSD-like support the function in general (those that support changing the file mode of symbolic links). Further, some examples of major implementations are added. Data for the BSDs taken from their online manpages. Signed-off-by: Christoph Anton Mitterer <[email protected]> Co-authored-by: Adam Turner <[email protected]>
…-107960) POSIX specifies that implementations are not required to support changing the file mode of symbolic links, but may do so. Consequently, `lchmod()` is not part of POSIX (but mentioned for implementations which do support the above). The current wording of the availability of `os.lchmod()` is rather vague and improved to clearly tell which POSIX/Unix/BSD-like support the function in general (those that support changing the file mode of symbolic links). Further, some examples of major implementations are added. Data for the BSDs taken from their online manpages. Signed-off-by: Christoph Anton Mitterer <[email protected]> Co-authored-by: Adam Turner <[email protected]>
POSIX specifies that implementations are not required to support changing the file mode of symbolic links, but may do so.
Consequently,
lchmod()
is not part of POSIX (but mentioned for implementations which do support the above).The current wording of the availability of
os.lchmod()
is rather vague and improved to clearly tell which POSIX/Unix/BSD-like support the function in general (those that support changing the file mode of symbolic links). Further, some examples of major implementations are added.Data for the BSDs taken from their online manpages.
os.lchmod()
is missing #107959📚 Documentation preview 📚: https://cpython-previews--107960.org.readthedocs.build/