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 jaraco
Recipients amaury.forgeotdarc, asvetlov, brian.curtin, eric.smith, giampaolo.rodola, jafo, jaraco, lemburg, loewis, nnorwitz, r.david.murray, ssbarnea, swarren
Date 2010-01-18.13:56:36
SpamBayes Score 0.0001092594
Marked as misclassified No
Message-id <1263822997.54.0.935658682658.issue1578269@psf.upfronthosting.co.za>
In-reply-to
Content
When I consider that the buildslaves are probably donated and not designated exclusively for Python testing, it makes good sense that they typically run under a restricted account.

Given that there is a specific permission that can be assigned to the buildslave user, it seems appropriate that the tests that attempt to create symlinks should fail if the user does not have that permission.

Martin, do you still prefer something that wraps tests that call symlink and only executes those tests if the current user context has that permission?
History
Date User Action Args
2010-01-18 13:56:37jaracosetrecipients: + jaraco, lemburg, loewis, nnorwitz, jafo, amaury.forgeotdarc, eric.smith, giampaolo.rodola, swarren, r.david.murray, ssbarnea, brian.curtin, asvetlov
2010-01-18 13:56:37jaracosetmessageid: <1263822997.54.0.935658682658.issue1578269@psf.upfronthosting.co.za>
2010-01-18 13:56:36jaracolinkissue1578269 messages
2010-01-18 13:56:36jaracocreate