[issue15352] importlib.h should be regenerated when the marshaling code changes
Meador Inge
report at bugs.python.org
Sun Jul 15 20:55:43 CEST 2012
Meador Inge <meadori at gmail.com> added the comment:
Eric, that is a good point, but if someone forgets (like I did) or just hasn't gotten around to bumping the number yet, then the build breaks because the interpreter crashes. I think we should always try to avoid building an interpreter that is in an inconsistent state.
Anyway, I am hitting another problem now -- _freeze_importlib is *not* idempotent. Thus adding this rule might cause some noise in the builds because importlib.h is different when nothing has actually changed. I am still investigating that problem.
Assuming I can fix the idempotency problem, then maybe _freeze_importlib should just be always run.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue15352>
_______________________________________
More information about the Python-bugs-list
mailing list