https://pantsbuild.org/ logo
Powered by
w

wide-midnight-78598

04/04/2023, 8:00 PM
If we're packaging pex files and python interpreters using 
scie
- is there a good reason to still have the 
pex_binary.entry_point
populated? I know it's optional, but could that interfere with the scie config? e.g. After using PEX_TOOLS to unpack and compile our application - I'm running my binary like this.
Copy code
"exe": "{scie.bindings.venv}/venv/bin/uvicorn",
              "args": [
                "apigateway.main:app"
              ]
Just wondering if I should keep my eye out for potential hiccups either at runtime, or in an upgrade workflow
With a BUILD of this:
Copy code
pex_binary(
  name="apigateway",
  dependencies=[
    ":libapigateway", 
    "//:reqs#uvicorn",
  ],
  output_path="backend/apigateway/apigateway.pex",
  include_tools=True,
e

enough-analyst-54434

04/24/2023, 6:10 PM
Sorry for the very late reply - missed this. Nope. If you don't need an entry point because your installing the PEX to a venv and using one of the venv console scripts as an entry point, you definitely don't need a separate PEX entrypoint. More generally there are 0 gotchas here. A scie just runs commands. It only interfaces with the filesystem and os exec facility.
w

wide-midnight-78598

04/24/2023, 6:49 PM
👍 Awesome, thanks!
Powered by