[Python-Dev] asdl.py and Python-ast.[hc] (original) (raw)

"Martin v. Löwis" martin at v.loewis.de
Fri Sep 27 16:26:07 CEST 2013

Am 26.09.13 15:52, schrieb Eli Bendersky:

* Should I always check-in Python-ast.h and Python-ast.c when I touch asdl* ? The generated files are unchanged, it's only the timestamp that changed.

If they really didn't change, I don't think it matters much. I believe there is a fundamental problem in Mercurial which fails to get it "right" - with the defense that one shouldn't check in generated files in the first place.

"hg touch" is supposed to work around this limitation. So when you only check in the generator, anybody updating should do "make touch" after the update, which should touch the generated files even though they didn't change.

* Can we, in theory, use new Pythons for asdl* code, because Python-ast.* are, in fact, checked in so they don't have to be rebuilt by the bots or users?

I'd say yes. That's the point of checking in generated files, so that users don't need to run the generator.

While we're at it, it seems that .hgtouch is wrong:

Include/ast.h: Parser/Python.asdl Parser/asdl.py Parser/asdlc.py Python/Python-ast.c: Include/ast.h The file Include/ast.h is not,

It may well be incorrect - feel free to fix it.

Regards, Martin

More information about the Python-Dev mailing list