Message159318
| Author |
lemburg |
| Recipients |
Arfrever, brett.cannon, eric.araujo, eric.smith, eric.snow, lemburg, ncoghlan, pitrou |
| Date |
2012年04月25日.16:46:09 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<4F982A4D.4020502@egenix.com> |
| In-reply-to |
<1335369747.82.0.825944228714.issue14657@psf.upfronthosting.co.za> |
| Content |
Nick Coghlan wrote:
>
> Nick Coghlan <ncoghlan@gmail.com> added the comment:
>
> At the very least, failing to regenerate importlib.h shouldn't be a fatal build error. It should just run with what its got, and hopefully you will get a working interpreter out the other end, such that you can regenerate the frozen module on the next pass.
>
> If we change that, then I'm OK with keeping the automatic rebuild.
I fixed that already today.
You now get a warning message from make, but no build error across
all buildbots like I had run into yesterday when working on the code. |
|