[issue21030] pip usable only by administrators on Windows and SELinux

Nick Coghlan added the comment: A little additional explanation of why the switch to copytree would have fixed this, at least in the SELinux case: under SELinux, files typically get labelled with a context based on where they're created. Copying creates a *new* file at the destination with the co

[issue21030] pip usable only by administrators on Windows and SELinux

Martin v. Löwis added the comment: Christian: thanks for the update. It's actually that the bug is fixed, not obsolete :-) -- resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue21030] pip usable only by administrators on Windows and SELinux

Donald Stufft added the comment: I believe in pip 1.5.6 we switched from shutil.move to shutil.copytree which I believe will reset the permissions/SELinux context? -- ___ Python tracker ___

[issue21030] pip usable only by administrators on Windows and SELinux

Christian Ullrich added the comment: Actually, this appears to be fixed in pip 1.5.6 (and 1.5.5, commit 79408cbc6fa5d61b74b046105aee61f12311adc9, AFAICT), which is included in 3.4.1; I cannot reproduce the problem in 3.4.1. That makes this bug obsolete. --

[issue21030] pip usable only by administrators on Windows and SELinux

Martin v. Löwis added the comment: If this needs to be done by fixing the ACLs afterwards, then I suggest to add a C custom action, based on the code in http://stackoverflow.com/questions/17536692/resetting-file-security-to-inherit-after-a-movefile-operation -- title: pip usable only b