Mercurial > hg
changeset 48299:1a420a13eeea
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
| author | Kyle Lippincott <spectral@google.com> |
|---|---|
| date | Wed, 03 Nov 2021 14:11:11 -0700 |
| parents | 6ffcaba7d122 |
| children | 9327ece2bc6f |
| files | rust/hgcli/pyoxidizer.bzl |
| diffstat | 1 files changed, 4 insertions(+), 1 deletions(-) [+] |
line wrap: on
line diff
--- a/rust/hgcli/pyoxidizer.bzl Wed Nov 03 12:35:57 2021 +0100 +++ b/rust/hgcli/pyoxidizer.bzl Wed Nov 03 14:11:11 2021 -0700 @@ -34,7 +34,10 @@ 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 = """