When calling `build.bat -d --regen' the graminit.c and graminit.h files are not generated with the following warnings:

Time Elapsed 00:02:49.06
  Killing any running python_d.exe instances...
  Getting build info from "C:\Program Files\Git\cmd\git.exe"
  Building heads/3.9-dirty:9e84a2c424 3.9
  pythoncore.vcxproj -> C:\Users\crm0376\source\repos\cpython\PCbuild\win32\python39_d.dll
  C:\Users\crm0376\source\repos\cpython\Parser\pgen\__main__.py:43: ResourceWarning: unclosed file <_io.TextIOWrapper name='C:\\Users\\crm0376\\source\\repos\\cpython\\PCbuild\\obj\\39win32_Debug\\regen\\graminit.h' mode='w' encoding='cp
  1252'>
    main()
  ResourceWarning: Enable tracemalloc to get the object allocation traceback
  C:\Users\crm0376\source\repos\cpython\Parser\pgen\__main__.py:43: ResourceWarning: unclosed file <_io.TextIOWrapper name='C:\\Users\\crm0376\\source\\repos\\cpython\\PCbuild\\obj\\39win32_Debug\\regen\\graminit.c' mode='w' encoding='cp
  1252'>
    main()
  ResourceWarning: Enable tracemalloc to get the object allocation traceback

Is this really worth our attention? In 3.10 this will be irrelevant.

Maybe I am doing something wrong.  I fetched the 3.10 alpha release, made a simple edit to line 93 in Grammer. 

pass_stmt: 'pass' | 'proceed'

Ran: 
>build.bat -d --regen

Successfully compiles with:
warning : Pegen updated. You will need to rebuild pythoncore to see the changes.

So I run:
> build.bat -d

But after all this I still get the runtime Name error that 'proceed' is not defined.

I have tried build.bat -t:cCleanAll bit it still does not work.  

Are there some extra steps with the new PEG parser?

Sorry, I realize what's wrong here. When we switched to the new PEG parser (the "pegen" you saw mentioned in the warning) we switched to a new grammar file. You have to change Grammar/python.gram instead of Grammar/Grammar.

We couldn't get rid of the Grammar/Grammar file yet because it's mentioned in the docs; this is pending a better way of producing https://docs.python.org/3.10/reference/grammar.html.

I hope this has informed you sufficiently; I don't think there's a bug that needs to be fixed on our end.

Thanks. I will check it out when I get back in front of my computer.

On Sat, Jul 25, 2020 at 4:22 PM Guido van Rossum <[email protected]>
wrote:

>
> Guido van Rossum <[email protected]> added the comment:
>
> Sorry, I realize what's wrong here. When we switched to the new PEG parser
> (the "pegen" you saw mentioned in the warning) we switched to a new grammar
> file. You have to change Grammar/python.gram instead of Grammar/Grammar.
>
> We couldn't get rid of the Grammar/Grammar file yet because it's mentioned
> in the docs; this is pending a better way of producing
> https://docs.python.org/3.10/reference/grammar.html.
>
> I hope this has informed you sufficiently; I don't think there's a bug
> that needs to be fixed on our end.
>
> ----------
> resolution:  -> not a bug
> stage:  -> resolved
> status: open -> closed
>
> _______________________________________
> Python tracker <[email protected]>
> <https://bugs.python.org/issue41362>
> _______________________________________
>

Thanks for the help.  I got my modification working by modifying the python.gram file and running build.bat --regen.