Marc-Andre Lemburg <m...@egenix.com> added the comment: Nick Coghlan wrote: > > Nick Coghlan <ncogh...@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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue14657> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
