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 db3l
Recipients brian.curtin, db3l, jeremy.kloth, jkloth, loewis, pitrou, python-dev, skrah, zach.ware
Date 2012-07-16.19:26:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1342466819.31.0.851200792575.issue15171@psf.upfronthosting.co.za>
In-reply-to
Content
It seems really unlikely to be related to this issue since I'm pretty sure build-amd64 doesn't get used on XP-4.

From the log it looks like it couldn't clean out and reuse the VS temporary build directory.  Manually cleaning it out and restarting the last build appears to have at least gotten past compiling.

I can't really explain why this was a problem, when I was able to manually remove the directory without error, and couldn't find any stray processes that may have been holding references to the files in that temporary directory.
History
Date User Action Args
2012-07-16 19:26:59db3lsetrecipients: + db3l, loewis, pitrou, jkloth, brian.curtin, skrah, jeremy.kloth, python-dev, zach.ware
2012-07-16 19:26:59db3lsetmessageid: <1342466819.31.0.851200792575.issue15171@psf.upfronthosting.co.za>
2012-07-16 19:26:58db3llinkissue15171 messages
2012-07-16 19:26:57db3lcreate