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 ncoghlan
Recipients Arfrever, brett.cannon, eric.araujo, eric.smith, eric.snow, lemburg, ncoghlan, pitrou, python-dev
Date 2012-06-25.00:40:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1340584804.25.0.773664455441.issue14657@psf.upfronthosting.co.za>
In-reply-to
Content
Given Antoine's other change to the build process to fix the bootstrapping problem, I'm OK with leaving it up to anyone hacking on _bootstrap.py to remember that they need to run make if they want the interpreter to see any of their changes.

Unlike the C accelerator cases, it's not possible for the two implementations to get out of sync on the buildbots, so running the tests twice would just be a convenience change for anyone hacking on _bootstrap.py rather than being needed for correctness.

That said, if someone created a new issue and posted a patch to run the tests twice, I wouldn't object - a classic case of +0 :)
History
Date User Action Args
2012-06-25 00:40:04ncoghlansetrecipients: + ncoghlan, lemburg, brett.cannon, pitrou, eric.smith, eric.araujo, Arfrever, python-dev, eric.snow
2012-06-25 00:40:04ncoghlansetmessageid: <1340584804.25.0.773664455441.issue14657@psf.upfronthosting.co.za>
2012-06-25 00:40:03ncoghlanlinkissue14657 messages
2012-06-25 00:40:02ncoghlancreate