Issue 9332: Document requirements for os.symlink usage on Windows (original) (raw)

Issue9332

Created on 2010-07-22 18:45 by brian.curtin, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (4)
msg111207 - (view) Author: Brian Curtin (brian.curtin) * (Python committer) Date: 2010-07-22 18:45
#1578269 introduced os.symlink support for Windows 6.0, but it requires the SeCreateSymbolicLinkPrivilege privilege to be enabled for the calling user, which is not always the case. Documentation needs to be added on the specific details here, possibly including a method to request privilege escalation.
msg112322 - (view) Author: Ned Batchelder (nedbat) * (Python triager) Date: 2010-08-01 13:00
This breaks virtualenv3 on Python 3.2, which simply test for the existence of os.symlink, which then fails for lack of privileges. Perhaps an os.can_symlink() method, returning a boolean? It can request privileges if you like, but provides a simple test that lets scripts know whether they should attempt a symlink or not.
msg112324 - (view) Author: Jason R. Coombs (jaraco) * (Python committer) Date: 2010-08-01 13:41
Ned, you bring up a good point. Please see #9333 for a discussion on the new os.symlink and privileges.
msg125292 - (view) Author: Brian Curtin (brian.curtin) * (Python committer) Date: 2011-01-04 04:11
Closed. I'll be adding this in #10608.
History
Date User Action Args
2022-04-11 14:57:04 admin set github: 53578
2011-01-04 04:11:42 brian.curtin set status: open -> closednosy:jaraco, eric.smith, nedbat, brian.curtinmessages: + superseder: [doc] Add a section to Windows FAQ explaining os.symlinkresolution: duplicatestage: needs patch -> resolved
2010-08-01 13:41:53 jaraco set messages: +
2010-08-01 13:00:16 nedbat set nosy: + nedbatmessages: +
2010-07-22 18:57:19 eric.smith set nosy: + eric.smith
2010-07-22 18:45:37 brian.curtin create