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 brian.curtin
Recipients brian.curtin, eric.smith, jaraco
Date 2010-08-02.21:31:06
SpamBayes Score 0.00023854035
Marked as misclassified No
Message-id <1280784667.96.0.721348368214.issue9333@psf.upfronthosting.co.za>
In-reply-to
Content
I'll have to investigate the possibility of the privilege occurring on XP -- I'm doubtful that it exists there, but I'll confirm.

Currently "os._symlink" is not exposed -- it gets swallowed up in Lib/os.py in the "nt" section starting on line 55 (it is available as nt._symlink, though). This is another point I need to confirm, but I don't think a process' available privileges can change during runtime, or at least I'm not familiar with that. For that reason, I just do the "enable_symlink()" on init and what happens there is what stays for the lifetime of the interpreter.

If available privileges can in fact change - and I'm not sure how we'd test that - "enable_symlink()" would have to be exposed.
History
Date User Action Args
2010-08-02 21:31:08brian.curtinsetrecipients: + brian.curtin, jaraco, eric.smith
2010-08-02 21:31:07brian.curtinsetmessageid: <1280784667.96.0.721348368214.issue9333@psf.upfronthosting.co.za>
2010-08-02 21:31:06brian.curtinlinkissue9333 messages
2010-08-02 21:31:06brian.curtincreate