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 zach.ware
Recipients brian.curtin, sbt, terry.reedy, tim.golden, zach.ware
Date 2013-03-10.23:12:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
>Terry J. Reedy added the comment:
>One must run external.bat if one is to subsequently build from the vs
>gui with *most* of the external dependencies. I think the command to
>run it should be 'external', not 'ready'. 'External' means get the
>external dependencies and anyone who has run external.bat will know
>what it means. 'Ready' does not mean anything in particular.

Fair point. Thinking about it again after some sleep, I agree. Next version will revert to 'external' rather than 'ready'.

>Just curious:
>Why do the buildbots run make clean before re-compiling? I seems like
>lots of extra work to re-compile things that are up to date?

I think the idea is to make sure everything is fresh, and avoid phantom problems from things that shouldn't cause problems, but do.

>What does running 'kill-python before re-building python do? I have not
>seen it mentioned in the in the devguide or pcbuild/readme.

I believe it's what actually performs the cleaning process. Tools/buildbot/clean.bat builds kill_python.exe and then runs it.
Date User Action Args
2013-03-10 23:12:34zach.waresetrecipients: + zach.ware, terry.reedy, tim.golden, brian.curtin, sbt
2013-03-10 23:12:33zach.warelinkissue16895 messages
2013-03-10 23:12:33zach.warecreate