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, ggenellina, giampaolo.rodola, jafo, jaraco, lemburg, loewis, nnorwitz, r.david.murray, ssbarnea, swarren
Date 2010-04-08.01:40:44
SpamBayes Score 0.014442592
Marked as misclassified No
Message-id <1270690847.18.0.714562756005.issue1578269@psf.upfronthosting.co.za>
In-reply-to
Content
I've been fighting a failing test in test_platform (when test.support.can_symlink() is True). Turns out the problem is caused by the fact that the Python DLL cannot be resolved when the executable isn't in the same directory (which is the case when launched from a symlink). I've created issue8342 to track this behavior.
History
Date User Action Args
2010-04-08 01:40:47jaracosetrecipients: + jaraco, lemburg, loewis, nnorwitz, jafo, amaury.forgeotdarc, ggenellina, eric.smith, giampaolo.rodola, swarren, r.david.murray, ssbarnea, brian.curtin, asvetlov
2010-04-08 01:40:47jaracosetmessageid: <1270690847.18.0.714562756005.issue1578269@psf.upfronthosting.co.za>
2010-04-08 01:40:45jaracolinkissue1578269 messages
2010-04-08 01:40:44jaracocreate