# HG changeset patch # User Kyle Lippincott # Date 2021-11-03 21:11:11 # Node ID 1a420a13eeea61e4ac3e4b188893d6356dfb8bb4 # Parent 6ffcaba7d1223a4ba7aff8befe2e7acaa8126ce1 pyoxidizer: use in-memory resources on non-Windows platforms In-memory resources were disabled for macOS in 7bc1beed, and for all platforms in c900d962. Unfortunately this made it so that we were no longer producing standalone binaries on these platforms, and would have to ship the .py and .pyc files alongside the pyoxidized binary. These changes are no longer necessary after f6b04591, which disabled pep517 and solved the issue we were encountering. Differential Revision: https://phab.mercurial-scm.org/D11734 diff --git a/rust/hgcli/pyoxidizer.bzl b/rust/hgcli/pyoxidizer.bzl --- a/rust/hgcli/pyoxidizer.bzl +++ b/rust/hgcli/pyoxidizer.bzl @@ -34,7 +34,10 @@ TIME_STAMP_SERVER_URL = VARS.get("TIME_S IS_WINDOWS = "windows" in BUILD_TARGET_TRIPLE -USE_IN_MEMORY_RESOURCES = False +# Use in-memory resources for all resources. If false, most of the Python +# stdlib will be in memory, but other things such as Mercurial itself will not +# be. See the comment in resource_callback, below. +USE_IN_MEMORY_RESOURCES = not IS_WINDOWS # Code to run in Python interpreter. RUN_CODE = """