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 gvanrossum
Recipients anthonypjshaw, gvanrossum, lys.nikolaou, pablogsal, paul.moore, pjx206, steve.dower, tim.golden, vstinner, zach.ware
Date 2021-03-29.23:22:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1617060150.04.0.457320787535.issue43567@roundup.psfhosted.org>
In-reply-to
Content
I've found build.bat --regen unreliable myself. I went over it with Steve and one issue that came up is that it uses the python.exe that is built to run the code generation scripts; OTOH on Linux/Mac these scripts are run using a suitable pre-existing Python binary, e.g. a recent enough system Python. (However, the frozen files require a binary (_freeze_importlib).

It will take some time to refactor things so that this is more usable.

Perhaps instead of (or in addition to) doing everything via .vcxproj files, we could have a simple(r) regen.bat script that runs all the regen scripts (or at least the non-freeze ones) using the system Python?

FWIW my own issues weren't with the parser, they were with regenerating opcode.h and opcode_targets.h.
History
Date User Action Args
2021-03-29 23:22:30gvanrossumsetrecipients: + gvanrossum, paul.moore, vstinner, tim.golden, zach.ware, steve.dower, anthonypjshaw, lys.nikolaou, pablogsal, pjx206
2021-03-29 23:22:30gvanrossumsetmessageid: <1617060150.04.0.457320787535.issue43567@roundup.psfhosted.org>
2021-03-29 23:22:30gvanrossumlinkissue43567 messages
2021-03-29 23:22:29gvanrossumcreate