Author tim.golden
Recipients eryksun, paul.moore, steve.dower, tim.golden, zach.ware
Date 2018-07-23.12:50:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1532350232.03.0.56676864532.issue34195@psf.upfronthosting.co.za>
In-reply-to
Content
I think I've got down to the determining factor. For info:

PYTHONHOME has nothing to do with it: the same thing happens if I cd into PCBuild\win32 and run python_d.exe directly

For historical reasons the directory in which I'm building (c:\work-in-progress) is actually a junction to c:\users\<me>\work-in-progress. There is some commentary in the API docs about traversing junctions, so presumably that's special-cased in some way which results in an uppercase drive letter.

If I rebuild in, eg, c:\temp which is a normal directory, I don't see the uppercase conversion. So, while I still need to fix the underlying test to be case-insensitive, it looks like the Mystery of the Uppercase Drive Letter is at least mostly solved.
History
Date User Action Args
2018-07-23 12:50:32tim.goldensetrecipients: + tim.golden, paul.moore, zach.ware, eryksun, steve.dower
2018-07-23 12:50:32tim.goldensetmessageid: <1532350232.03.0.56676864532.issue34195@psf.upfronthosting.co.za>
2018-07-23 12:50:32tim.goldenlinkissue34195 messages
2018-07-23 12:50:31tim.goldencreate