kind-knife-4981703/09/2021, 4:21 PM
something that will never resolve in windows. It's even part of the tl/dr ! https://pex.readthedocs.io/en/latest/whatispex.html#tl-dr That raises some questions: For window support would we be willing to (just for windows users) drop the idea of being able to execute a .pex file alone. Example: https://github.com/pantsbuild/pex/blob/master/tests/tools/commands/test_venv.py#L533 changing to
And then in general, are we ready to have different paths in a few places the code base with a few
subprocess.check_call(args=[sys.executable, "-mpex", pex_file, "venv", venv], env=make_env(PEX_TOOLS=1))
statements that will be required to achieve first party support for windows?
hundreds-father-40403/09/2021, 5:55 PM
Working through adding windows support for pex.Woot, thanks! Check out the #pex channel also
For window support would we be willing to (just for windows users) drop the idea of being able to execute a .pex file alone.What would be the purpose of Pex here? I get the general notion of "I want to bundle all my deps and code into a single file", but then I don't know how users would end up actually consuming that file
Also makes me start thinking, can there be the idea of two different levels of supportGenerally, I think we'd be pretty hesitant to do this. It greatly adds to complexity to have to keep track of which functionality maps to what. And it's confusing for users to know what can and cannot be used For example, if we hooked up Windows-compatible Pex to Pants via
, what would Pants do if a user tried to set a field like
that (for the sake of argument) does not work on Windows because it's tier 1
witty-crayon-2278603/09/2021, 6:07 PM
clean-city-6447203/09/2021, 6:21 PM
. That will help guide how we approach the problems we are seeing in the tests.
kind-knife-4981703/10/2021, 5:25 PM