Author jaraco
Recipients amaury.forgeotdarc, asvetlov, brian.curtin, eric.smith, ggenellina, giampaolo.rodola, jafo, jaraco, lemburg, loewis, nnorwitz, r.david.murray, ssbarnea, swarren
Date 2010-01-26.01:53:32
SpamBayes Score 1.7993e-05
Marked as misclassified No
Message-id <1264470827.17.0.107077838739.issue1578269@psf.upfronthosting.co.za>
In-reply-to
Content
Amaury, that was a good suggestion, but I did with Eric's help track down a mechanism to test for the presence of the symlink creation privilege. I prefer to have a proper check rather than to attempt to create one and test for the failure message because it doesn't have the potential to be confounded with other causes. I want to avoid issues such as where is the test symlink created and how is it cleaned up. If there's still desire to go that route after looking at this implementation, I'm not opposed to switching gears and using that technique.

This patch (20) uses ctypes (in the test suite; is that okay?) to determine if the symlink creation privilege is present, falling back to the assumption that it is, and integrates that with the test.support.has_symlink function (which is new in this issue thread).

Eric, can you test this new patch in your limited user environment and report what you find?
History
Date User Action Args
2010-01-26 01:53:48jaracosetrecipients: + jaraco, lemburg, loewis, nnorwitz, jafo, amaury.forgeotdarc, ggenellina, eric.smith, giampaolo.rodola, swarren, r.david.murray, ssbarnea, brian.curtin, asvetlov
2010-01-26 01:53:47jaracosetmessageid: <1264470827.17.0.107077838739.issue1578269@psf.upfronthosting.co.za>
2010-01-26 01:53:45jaracolinkissue1578269 messages
2010-01-26 01:53:45jaracocreate