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 eryksun
Recipients antoine.pietri, eryksun, larry, mshuffett, ned.deily, pitrou, richardc, serhiy.storchaka, steve.dower, zach.ware, zopieux
Date 2017-06-01.00:42:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1496277765.17.0.176055397173.issue30177@psf.upfronthosting.co.za>
In-reply-to
Content
> Ah, looks like they require symlinks for the whole test, 
> which means you need to be admin when running them on Windows.

The privilege to create symlinks isn't filtered out of a standard user's token. Are there any buildbots already running as a standard user? In that case it may be simpler to modify the user's rights via secpol.msc: Local Policies -> User Rights Assignment -> Create symbolic links.

Support could also be added for the new feature in Windows 10 to allow unprivileged creation of symlinks when the system is in developer mode and the flag SYMBOLIC_LINK_FLAG_ALLOW_UNPRIVILEGED_CREATE [1] is used. A keyword-only option to use this flag could be backported to 3.6 and enabled by default in 3.7.

[1]: https://blogs.windows.com/buildingapps/2016/12/02/symlinks-windows-10
History
Date User Action Args
2017-06-01 00:42:45eryksunsetrecipients: + eryksun, pitrou, larry, ned.deily, zach.ware, serhiy.storchaka, steve.dower, antoine.pietri, mshuffett, zopieux, richardc
2017-06-01 00:42:45eryksunsetmessageid: <1496277765.17.0.176055397173.issue30177@psf.upfronthosting.co.za>
2017-06-01 00:42:45eryksunlinkissue30177 messages
2017-06-01 00:42:44eryksuncreate