Hello again - another pex question. Is there an easy way to create a venv for a pex that was built without

--include-tools

or

--venv

? I found a roundabout way to do this, is there something simpler?

pex --include-tools -o just-tools.pex
PEX_TOOLS=1 PEX_PATH=the-pex-without-tools.pex ./just-tools.pex venv my-venv

While can build our user's newer pexes with

--include-tools

, we also need to support their older pexes which were not built with tools.

You can use the pex-tools console script. When you install pex in a venv you get

pex

,

pex3

and

pex-tools

. It's then

pex-tools any.pex ...

ok that makes a lot more sense 🙂. we use the

pex

console script during build. i think we install

pex

in the run environment as well so

pex-tools

should be available.

For the Pex PEX its:

jsirois@Gill-Windows:~ $ curl -fsLO <https://github.com/pantsbuild/pex/releases/download/v2.1.118/pex>
jsirois@Gill-Windows:~ $ chmod +x pex
jsirois@Gill-Windows:~ $ ./pex cowsay -ccowsay -ocowsay.pex
jsirois@Gill-Windows:~ $ PEX_SCRIPT=pex-tools ./pex cowsay.pex venv here
jsirois@Gill-Windows:~ $ here/pex 'Moo!'
  ____
| Moo! |
  ====
    \
     \
       ^__^
       (oo)\_______
       (__)\       )\/\
           ||----w |
           ||     ||

nice. looks like we do have

/usr/local/bin/pex-tools

in our runtime environment so I can just use that.

Great

ah ok. we use

--python=

but not

--interpreter-constraint=

. at least currently we only have one python in each runtime image and have separate images for different python versions.