This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ischwabacher
Recipients Jey.Narasimhan, ischwabacher, ned.deily, pitrou, r.david.murray
Date 2015-03-01.21:54:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1425246898.14.0.509961318475.issue20876@psf.upfronthosting.co.za>
In-reply-to
Content
This behavior is caused by the way NFS clients implement unlinking open files: instead of unlinking an open file, the filesystem renames it to .nfsXXXX and unlinks it on close.  (The search term you want is "silly rename".)  The reason this problem appears is that `test.support.fs_is_case_insensitive()` unlinks but fails to close the temporary file that it creates.  Of course, any attempt to unlink the .nfsXXXX file (for instance, by `shutil.rmtree`) just succeeds in renaming it to .nfsYYYY, so there is no way to delete the parent directory until the file is closed.

The attached patch modifies the offending function to use the `tempfile.NamedTemporaryFile` context manager, which closes the file on leaving the block.
History
Date User Action Args
2015-03-01 21:54:58ischwabachersetrecipients: + ischwabacher, pitrou, ned.deily, r.david.murray, Jey.Narasimhan
2015-03-01 21:54:58ischwabachersetmessageid: <1425246898.14.0.509961318475.issue20876@psf.upfronthosting.co.za>
2015-03-01 21:54:58ischwabacherlinkissue20876 messages
2015-03-01 21:54:58ischwabachercreate