When I spawn subprocesses from my `pex_binary` the...
# generals
straight-action-80318
07/20/2022, 9:16 PMWhen I spawn subprocesses from my
pex_binary✅ 1
b
bitter-ability-32190
07/20/2022, 9:23 PMAre they Python subprocesses?
s
straight-action-80318
07/20/2022, 9:24 PMYeah
b
bitter-ability-32190
07/20/2022, 9:24 PMIf so, this is "fixed" in newer PEX (therefore newer Pants)
See https://github.com/pantsbuild/pex/issues/1825
There's also a workaround of setting
PYTHONPATHenvsys,paths
straight-action-80318
07/20/2022, 9:26 PMoh nice, timely
straight-action-80318
07/20/2022, 9:26 PMdo you know what release I need to pick this change up?
b
bitter-ability-32190
07/20/2022, 9:29 PMI just switched to mobile, so I couldn't tell you immediately.
There's also support to use newer PEX in an older Pants, but YMMV
bitter-ability-32190
07/20/2022, 9:29 PMs
straight-action-80318
07/20/2022, 9:33 PMokay I think this is working with the latest RC that’ll be okay at least for now
straight-action-80318
07/20/2022, 9:33 PMthanks!
b
bitter-ability-32190
07/20/2022, 9:34 PMHot tip, invoke code using -m and the module name. And make sure the module is in its own string. Then enable Pants string import inference 😉
n
nice-florist-55958
07/21/2022, 1:42 AMDoes this mean we don't need
env={**os.environ, **{“PYTHONPATH”: “:”.join(sys.path)}}h
happy-kitchen-89482
07/21/2022, 2:30 AMI believe so
5 Views