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 brett.cannon, eli.bendersky, eric.snow, ncoghlan
Date 2013-11-19.14:30:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1384871452.79.0.559077808512.issue19655@psf.upfronthosting.co.za>
In-reply-to
Content
FWIW, asdl_c.py could use some "modernization", but I'll defer this to a later cleanup in order to do things gradually.

The same can be said for the Makefile rules - they can be simpler and more efficient (no need to invoke asdl_c / parse the ASDL twice, for example).

Incidentally, where would be a good place to put the ASDL tests? Can/should we reach into the Parser/ directory when running the Python regression tests (will this even work in an installed Python)? Or should I just plop asdl_test.py alongside asdl.py and mention that it should be run when asdl.py changes?
History
Date User Action Args
2013-11-19 14:30:52eli.benderskysetrecipients: + eli.bendersky, brett.cannon, ncoghlan, eric.snow
2013-11-19 14:30:52eli.benderskysetmessageid: <1384871452.79.0.559077808512.issue19655@psf.upfronthosting.co.za>
2013-11-19 14:30:52eli.benderskylinkissue19655 messages
2013-11-19 14:30:52eli.benderskycreate