[issue24738] os.link() issues on Windows & ReFS

Changes by R. David Murray : -- resolution: -> third party stage: -> resolved status: open -> closed type: crash -> behavior ___ Python tracker ___

[issue24738] os.link() issues on Windows & ReFS

eryksun added the comment: The problem is that the 3rd party [lockfile][1] module assumes that if os.link exists it means hard links are supported for all file systems on a given platform. So in your case it gets stuck repeatedly trying an operation that can never succeed. This can probably be

[issue24738] os.link() issues on Windows & ReFS

Harry Lam added the comment: Slight bit of clarification: This doesn't affect all scripts -- just those which don't have proper Except OSError handling. In pip's case, a timeout is not passed to the acquire() function when it is first being called and causes this issue with hanging. -

[issue24738] os.link issues on Windows & ReFS

New submission from Harry Lam (WaXHeLL): Storage Spaces (RAID volumes) under Windows 8.1 / Server 2012 R2 use ReFS which does not support hard links. If the Users directory has been moved to a ReFS volume, it causes any script that uses os.link to hang (pip is one of the notable examples). As