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 twouters
Recipients benjamin.peterson, eric.araujo, ezio.melotti, kushal.das, loewis, python-dev, twouters, vstinner
Date 2014-04-16.21:06:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
FYI, this broke building in a separate object directory (again!) for multiple reasons: it's running the script without specifying $(srcdir), and it's writing to $(srcdir)/Include/opcode.h (where $(srcdir) may be unwritable), and it's picking up the wrong opcode module: the sys.path mucking in Tools/ isn't inserting the right directory for 'import opcode' to pick up the target-Python's It should probably be using execfile() and have the name of the file passed in, instead.

Even if it were importing the right, relying on 'import' or 'execfile' here sounds like a bad idea: it means the opcode module of the *target* Python needs to be compatible with the Python that the script runs with. Since the syntax of opcode.h is much more constrained, a more flexible approach, in my opinion, would be to parse opcode.h to produce (or an with just the definitions, that would then import.)
Date User Action Args
2014-04-16 21:06:23twouterssetrecipients: + twouters, loewis, vstinner, benjamin.peterson, ezio.melotti, eric.araujo, python-dev, kushal.das
2014-04-16 21:06:23twouterssetmessageid: <>
2014-04-16 21:06:23twouterslinkissue17861 messages
2014-04-16 21:06:23twouterscreate