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 eli.bendersky
Recipients BreamoreBoy, benjamin.peterson, brett.cannon, eli.bendersky, eric.snow, larry, ncoghlan, skrah, techtonik
Date 2013-11-24.22:53:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAF-Rda8WDrsUDqtHCdk4PoMt4YaMH0+sUh-otKf=iCge2nS_jA@mail.gmail.com>
In-reply-to <1385326540.67.0.671239005192.issue19655@psf.upfronthosting.co.za>
Content
Larry Hastings added the comment:

>
> Are the generated files *byte for byte* the same as produced by the
> existing parser generation process?
>

Correct. The generator runs during the build (in the Makefile), but only if
the files were out-of-date. It takes Python.asdl and produces Python-ast.h
and Python-ast.c; the latter two are compiled into the CPython executable.
The .h/.c files produced by my alternative generator are exactly identical
to the ones in there now.

I don't feel strongly about this, but I may need a refresher in the release
process rules. From today and until Feb 23rd, 2014 - are we not supposed to
be adding new features/PEPs or are we also not supposed to do any code
refactorings and/or any changes at all unless those are directly related to
fixing a specific bug/issue?
History
Date User Action Args
2013-11-24 22:53:03eli.benderskysetrecipients: + eli.bendersky, brett.cannon, ncoghlan, larry, techtonik, benjamin.peterson, skrah, BreamoreBoy, eric.snow
2013-11-24 22:53:03eli.benderskylinkissue19655 messages
2013-11-24 22:53:02eli.benderskycreate