tests/test-patch.t

make: switch the PYTHON default to `py.exe -3` on Windows

Python3 _is_ named `python.exe` on Windows, but that isn't necessarily on PATH
when installing from python.org.  I do happen to have a python.exe on PATH in
`$LOCALAPPDATA/Microsoft/WindowsApps`, but it appears to be 0 bytes (likely
because of permission issues), and doesn't run:

    $ python -V
     - Cannot open

Pulkit hit the same error as I did though, so it isn't just my system:

    $ make -C . local
    make: Entering directory `/home/Dell/repos/hg-committed`
    python setup.py  \
              build_py -c -d . \
              build_ext  -i \
              build_hgexe  -i \
              build_mo
     - Cannot openmake: *** [local] Error 1

The `py.exe` dispatcher lives in the Windows directory (so it is on PATH), looks
up the python.org installation, and invokes that interpreter directly.  I get a
warning with py39, but if it's our issue, it was an existing one:

    $ make -C .. local
    make: Entering directory `/c/Users/Matt/hg'
    py -3 setup.py  \
              build_py -c -d . \
              build_ext  -i \
              build_hgexe  -i \
              build_mo
    C:\Users\Matt\AppData\Local\Programs\Python\Python39\lib\site-packages\setuptools\distutils_patch.py:25:
        UserWarning: Distutils was imported before Setuptools. This usage is discouraged and may
        exhibit undesirable behaviors or errors. Please use Setuptools' objects directly or at least
        import Setuptools first.
      warnings.warn(

The end result is a py3 based hg.exe that annoyingly won't run because it can't
find python39.dll.  It will run tests (the ones without the `python3` shbang
line anyway), because the test runner adjusts PATH to include the python running
it.

Differential Revision: https://phab.mercurial-scm.org/D9361

  $ cat > patchtool.py <<EOF
  > from __future__ import absolute_import, print_function
  > import sys
  > print('Using custom patch')
  > if '--binary' in sys.argv:
  >     print('--binary found !')
  > EOF

  $ echo "[ui]" >> $HGRCPATH
  $ echo "patch=\"$PYTHON\" ../patchtool.py" >> $HGRCPATH

  $ hg init a
  $ cd a
  $ echo a > a
  $ hg commit -Ama -d '1 0'
  adding a
  $ echo b >> a
  $ hg commit -Amb -d '2 0'
  $ cd ..

This test checks that:
 - custom patch commands with arguments actually work
 - patch code does not try to add weird arguments like
 --binary when custom patch commands are used. For instance
 --binary is added by default under win32.

check custom patch options are honored

  $ hg --cwd a export -o ../a.diff tip
  $ hg clone -r 0 a b
  adding changesets
  adding manifests
  adding file changes
  added 1 changesets with 1 changes to 1 files
  new changesets 8580ff50825a
  updating to branch default
  1 files updated, 0 files merged, 0 files removed, 0 files unresolved

  $ hg --cwd b import -v ../a.diff
  applying ../a.diff
  Using custom patch
  applied to working directory

Issue2417: hg import with # comments in description

Prepare source repo and patch:

  $ rm $HGRCPATH
  $ hg init c
  $ cd c
  $ printf "a\rc" > a
  $ hg ci -A -m 0 a -d '0 0'
  $ printf "a\rb\rc" > a
  $ cat << eof > log
  > first line which can't start with '# '
  > # second line is a comment but that shouldn't be a problem.
  > A patch marker like this was more problematic even after d7452292f9d3:
  > # HG changeset patch
  > # User lines looks like this - but it _is_ just a comment
  > eof
  $ hg ci -l log -d '0 0'
  $ hg export -o p 1
  $ cd ..

Clone and apply patch:

  $ hg clone -r 0 c d
  adding changesets
  adding manifests
  adding file changes
  added 1 changesets with 1 changes to 1 files
  new changesets 7fadb901d403
  updating to branch default
  1 files updated, 0 files merged, 0 files removed, 0 files unresolved
  $ cd d
  $ hg import ../c/p
  applying ../c/p
  $ hg log -v -r 1
  changeset:   1:cd0bde79c428
  tag:         tip
  user:        test
  date:        Thu Jan 01 00:00:00 1970 +0000
  files:       a
  description:
  first line which can't start with '# '
  # second line is a comment but that shouldn't be a problem.
  A patch marker like this was more problematic even after d7452292f9d3:
  # HG changeset patch
  # User lines looks like this - but it _is_ just a comment
  
  

Error exit (issue4746)

  $ cat >> exit1.py <<EOF
  > import sys
  > sys.exit(1)
  > EOF

  $ hg import ../c/p --config ui.patch="\"$PYTHON\" \"`pwd`/exit1.py\""
  applying ../c/p
  abort: patch command failed: exited with status 1
  [255]

  $ cd ..