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 eric.snow, eryksun, jkloth, lukasz.langa, mattip, ncoghlan, paul.moore, ralf.gommers, steve.dower, tim.golden, zach.ware
Date 2019-03-28.01:44:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> There are no specific "import" tests, because it's such a pain to set 
> those up (I need to delete files from the build directory during the 
> test, and if other tests have already used them that will fail, or I 
> need to copy the Python install elsewhere so it doesn't pick those
> up). 

Instead of copying the whole install, you should be able to symlink the core binaries (e.g. python.exe, python38.dll, python3.dll, vcruntime140.dll) to a temporary directory and set PYTHONHOME. Most (or at least some) of the build bots should be set up to grant the symlink privilege to the current user or all standard users, and %TEMP% should be on an NTFS/ReFS volume that supports reparse points.
Date User Action Args
2019-03-28 01:44:57eryksunsetrecipients: + eryksun, paul.moore, ncoghlan, tim.golden, jkloth, lukasz.langa, eric.snow, zach.ware, mattip, steve.dower, ralf.gommers
2019-03-28 01:44:57eryksunsetmessageid: <>
2019-03-28 01:44:57eryksunlinkissue36085 messages
2019-03-28 01:44:56eryksuncreate