Message 159318 - Python tracker

➜

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	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.

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.

History
Date	User	Action	Args
2012-04-25 16:46:10	lemburg	set	recipients: + lemburg, brett.cannon, ncoghlan, pitrou, eric.smith, eric.araujo, Arfrever, eric.snow
2012-04-25 16:46:09	lemburg	link	issue14657 messages
2012-04-25 16:46:09	lemburg	create