Skip to content
Snippets Groups Projects
  1. Oct 18, 2021
    • Kyle Lippincott's avatar
      pyoxidizer: update README.md with several small fixes · 16c3fe46929a
      Kyle Lippincott authored
      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
      16c3fe46929a
  2. Mar 25, 2021
  3. Apr 01, 2020
    • Gregory Szorc's avatar
      hgcli: customize for Mercurial · bc847878f4c0
      Gregory Szorc authored
      Now that we have a shiny new PyOxidizer-based hgcli project, let's
      customize it for Mercurial!
      
      This commit replaces the auto-generated pyoxidizer.bzl with one
      that installs Mercurial from the local source repository.
      
      A README.md with build instructions has been added.
      
      The Cargo.toml file has been updated to reflect the proper license
      and reference the added README.md.
      
      In my Linux environment, running the test suite yields 27 failures.
      
      It's worth noting the run time of the test harness on Linux on my
      Ryzen 3950X:
      
      before: 378s wall; 9982s user; 1195s sys
      after:  353s wall; 8996s user;  958s sys
      % orig: 93.4 wall;  90.1  user; 80.2 sys
      
      While I haven't measured explicitly, I suspect the performance win is
      due to in-memory resource loading (which is known to be faster than
      Python's filesystem importer).
      
      Differential Revision: https://phab.mercurial-scm.org/D8351
      bc847878f4c0
Loading