pyoxidizer: update README.md with several small fixes

Currently, pyoxidizer.bzl does not mention the git commit that should be checked
out, so these instructions are a bit difficult to follow right now (impossible,
technically), so I removed the instruction to `git checkout <Git commit>` and
the admonition to use a specific version of PyOxidizer. I don't even know if the
project currently builds with the "0.7.0-pre" version that was previously
recommended.

As fallout from that change to not "pin" to a specific PyOxidizer, I had to
update the Python version to use when running the tests.

While here, I added a recommendation to use `--release`, as the primary reason
for this project is performance, and it may have been leaving some on the table
to not have that there.

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

rust/hgcli/README.md

@@ -1,50 +1,48
 # Oxidized Mercurial
 
 This project provides a Rust implementation of the Mercurial (`hg`)
 version control tool.
 
 Under the hood, the project uses
 [PyOxidizer](https://github.com/indygreg/PyOxidizer) to embed a Python
 interpreter in a binary built with Rust. At run-time, the Rust `fn main()`
 is called and Rust code handles initial process startup. An in-process
 Python interpreter is started (if needed) to provide additional
 functionality.
 
 # Building
 
-This project currently requires an unreleased version of PyOxidizer
-(0.7.0-pre). For best results, build the exact PyOxidizer commit
-as defined in the `pyoxidizer.bzl` file:
+First, acquire and build a copy of PyOxidizer; you probably want to do this in
+some directory outside of your clone of Mercurial:
 
     $ git clone https://github.com/indygreg/PyOxidizer.git
     $ cd PyOxidizer
-    $ git checkout <Git commit from pyoxidizer.bzl>
     $ cargo build --release
 
-Then build this Rust project using the built `pyoxidizer` executable::
+Then build this Rust project using the built `pyoxidizer` executable:
 
-    $ /path/to/pyoxidizer/target/release/pyoxidizer build
+    $ /path/to/pyoxidizer/target/release/pyoxidizer build --release
 
 If all goes according to plan, there should be an assembled application
-under `build/<arch>/debug/app/` with an `hg` executable:
+under `build/<arch>/release/app/` with an `hg` executable:
 
-    $ build/x86_64-unknown-linux-gnu/debug/app/hg version
+    $ build/x86_64-unknown-linux-gnu/release/app/hg version
     Mercurial Distributed SCM (version 5.3.1+433-f99cd77d53dc+20200331)
     (see https://mercurial-scm.org for more information)
 
     Copyright (C) 2005-2020 Olivia Mackall and others
     This is free software; see the source for copying conditions. There is NO
     warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
 
 # Running Tests
 
 To run tests with a built `hg` executable, you can use the `--with-hg`
 argument to `run-tests.py`. But there's a wrinkle: many tests run custom
 Python scripts that need to `import` modules provided by Mercurial. Since
 these modules are embedded in the produced `hg` executable, a regular
 Python interpreter can't access them! To work around this, set `PYTHONPATH`
 to the Mercurial source directory. e.g.:
 
     $ cd /path/to/hg/src/tests
-    $ PYTHONPATH=`pwd`/.. python3.7 run-tests.py \
-        --with-hg `pwd`/../rust/hgcli/build/x86_64-unknown-linux-gnu/debug/app/hg
+    $ PYTHONPATH=`pwd`/.. python3.9 run-tests.py \
+        --with-hg `pwd`/../rust/hgcli/build/x86_64-unknown-linux-gnu/release/app/hg