Read about our upcoming Code of Conduct on this issue

Commit c0867f10 authored by Kyle Lippincott's avatar Kyle Lippincott
Browse files

pyoxidizer: use in-memory resources on non-Windows platforms

In-memory resources were disabled for macOS in 7bc1beedd718, and for all platforms
in c900d962e38b. 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 f6b045910d82, which disabled pep517 and
solved the issue we were encountering.

Differential Revision: https://phab.mercurial-scm.org/D11734
parent 6ffcaba7d122
Pipeline #28633 failed with stages
in 60 minutes and 26 seconds
......@@ -34,7 +34,10 @@ TIME_STAMP_SERVER_URL = VARS.get("TIME_STAMP_SERVER_URL", "http://timestamp.digi
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 = """
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment