-
-
Notifications
You must be signed in to change notification settings - Fork 30.3k
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
add os.chflags() and os.lchflags() where available #43370
Comments
The return value from os.stat() includes st_flags on some systems, but |
Logged In: YES Patch looks good. Do we want to include it? |
Logged In: YES What operating systems is this available on? The only one As far as the patch itself, it looks good. There are a Also would need to update Misc/NEWS and ACKS if accepted. |
Logged In: YES In addition to MacOS, chflags(2) is available on FreeBSD, Thanks for the comments - I've attached an updated version |
Thanks for the patch. Committed as r53826. |
It looks like Tru64 does have some version of chflags, however, it is undocumented and apparently causes python to exit. It is at least one of the reasons for the recent buildbot failures: http://python.org/dev/buildbot/all/alpha%20Tru64%205.1%20trunk/builds/1550/step-test/0 That doesn't really tell the whole story, but I logged on to the machine and ran the test, after modifying unittest to flush the stream, sigh :-( and got this: ringneck:/net/cci/nnorwitz/python/trunk.norwitz-tru64/nn-work-build % ./python -E -tt ./Lib/test/regrtest.py -v test_posix |
nnorwitz, can you please report whether the attached patch fixes it? |
Martin's patch from 2007-03-21 fixed the problem with test_posix. It I think it is good to apply this patch. |
Committed chflags.diff as r59317. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: