[issue30749] Non-atomic and unusual (wrong) rename behavior under OS X

Alex Groce added the comment: Looks to be OS X rename, not Python -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker

[issue30749] Non-atomic and unusual (wrong) rename behavior under OS X

Alex Groce added the comment: #include #include #include #include int main () { system("rm -rf testingdir"); mkdir("testingdir",S_IRWXU); mkdir("testingdir/a",S_IRWXU); mkdir("testingdir/a/a",S_IRWXU); mkdir("testingdir/a/a/a",S_IRWXU); printf("BEFORE:\n"); system("ls -lR

[issue30749] Non-atomic and unusual (wrong) rename behavior under OS X

Alex Groce added the comment: Tested on latest Mac OS; mv at command line does the right thing, have not checked a C rename yet. -- ___ Python tracker

[issue30749] Non-atomic and unusual (wrong) rename behavior under OS X

Ronald Oussoren added the comment: What version of macOS did you test on? -- ___ Python tracker ___ ___

[issue30749] Non-atomic and unusual (wrong) rename behavior under OS X

Alex Groce added the comment: Checked, and this is a problem on Python 3 as well as 2.7. -- title: Non-atomic and unusual (wrong) rename behavior under OS X, Python 2.7.13 -> Non-atomic and unusual (wrong) rename behavior under OS X versions: -Python 2.7

[issue30749] Non-atomic and unusual (wrong) rename behavior under OS X, Python 2.7.13

New submission from Alex Groce: Attached file causes a failed rename, which is fine. However, after the failed rename, the directory structure has changed (and the error reported is not very helpful). Behavior does not match Linux or Windows behavior. Discovered using random testing to