Running Python from the source repo

[Terry Reedy]

On 8/8/2016 12:24 PM, Zachary Ware wrote:

> I generally assume that if I'm testing a patch, I'm going to need to
> rebuild regardless of what the patch actually touches.  I often wait
> until the patch is applied before I do the rebuild, or if I'm manually
> testing a bug I go ahead and do the rebuild immediately.  Most make
> targets (including 'test') will go ahead make sure the build is up to
> date without your input.  Usually the slowest part of a rebuild is
> rerunning ./configure, which 'make' will do for you if it determines
> that it should.  You can speed up ./configure by passing it the
> '--config-cache' (or '-C') option.  If you're on a multi-core machine,
> also remember to pass '-j<number of cores + 1>' to make to speed up
> building, and also to regrtest (which you can do with 'make test
> TESTOPTS=-j9') to speed up testing.
>
> [1]https://www.mercurial-scm.org/wiki/FetchExtension

Last January, I wrote a batch file to build all three versions with the 
'optional' extensions.  I started rebuilding more often after this.

36\pcbuild\build.bat -e -d
35\pcbuild\build.bat -e -d
27\pcbuild\build.bat -e -d

Thanks for making this possible.  It initially worked, but now it stops 
after the first command, even without errors.  Has a flag been changed 
to treat warnings as errors?  How can I change the .bat to wrap each 
command with the equivalent of try: except: pass?

-- 
Terry Jan Reedy