How do I upgrade the

pip

inside of the

venv

for a package in my

PEX_ROOT

? I upgraded system

pip

, but the

pip

inside the

venv

doesn't seem to mirror it. ( which aligns with `venv`s) Specifically, installing

cryptography

is failing, and I think a newer pip would bypass the build and download built wheels?

1st off, Pex is hermetic as its ~1st rule. Your system foo should have no effect on it in any aspect if Pex works right. How did you get a pip in your venv in the PEX_ROOT? For venvs you create manually, there is `--pip`:

$ pex-tools /dev/null venv -h
usage: pex-tools PATH venv [-h] [--scope {all,deps,srcs}] [-b {false,prepend,append}] [-f] [--collisions-ok] [-p] [--copies] [--compile] [--prompt PROMPT] [--rm {pex,all}] [--emit-warnings] [--pex-root PEX_ROOT] [--disable-cache] [--cache-dir CACHE_DIR] [--tmpdir TMPDIR]
                           [--rcfile RC_FILE]
                           PATH

Creates a venv from the PEX file.

positional arguments:
  PATH                  The directory to create the virtual environment in.

options:
  -h, --help            show this help message and exit
  --scope {all,deps,srcs}
                        The scope of code contained in the Pex that is installed in the venv. By defaultall code is installed and this is generally what you want. However, in some situations it's beneficial to split the venv installation into deps and srcs steps. This is
                        particularly useful when installing a PEX in a container image. See <https://pex.readthedocs.io/en/latest/recipes.html#pex-app-in-a-container> for more information. (default: all)
  -b {false,prepend,append}, --bin-path {false,prepend,append}
                        Add the venv bin dir to the PATH in the __main__.py script. (default: false)
  -f, --force           If the venv directory already exists, overwrite it. (default: False)
  --collisions-ok       Don't error if population of the venv encounters distributions in the PEX file with colliding files, just emit a warning. (default: False)
  -p, --pip             Add pip to the venv. (default: False)

You should be able to use that pip to upgrade itself to any version you like.

How did you get a pip in your venv in the PEX_ROOT?

This is through Pants, so whatever Pants PEX incantations

Huh, ... is this from

./pants export

?

No. Specifically I'm locking my

flake8

resolve, and on CI when trying to build the PEX it's started to build cryptography

Ok, your terminology threw me off I think. You should find no

pip

in your venvs under the PEX_ROOT. Are you referring to the

pip

pex

uses to build your PEX? That's a vendored

pip

and you cannot upgrade it.

This

/home/buildagent/.cache/pants/named_caches/pex_root/venvs/s/3663269c/venv/lib/python3.8/site-packages/pip

doens't look like vendored pip to me 🤔

Probabaly a pep-517 build of an sdist in the resolve.

Ahhhhhhhhh

The `poetry-core`provides a PEP-517 build backend alot of folks use.

I've got VCS reqs, I bet one of them uses

poetry

What does coke mean for you? The history is Eric Ayers from Square in Atlanta - where coke is headquartered - and he is as old as me and refers to "You owe me a coke!" when you say the ~same thing as someone else at the ~same time.

IDK I saw Eric do it for "you win a coke, thats it"

Ah, ok. The origin was the opposite - you lose a coke!

This is a CI machine, so admittedly a bit hard to run cod eon

Just running on your machine is fine. That will give good info to start.

FWIW I can't repo, but I also have a rust compiler so that mightve been hidden from me and I didn't know

I'm confused - that has 0 production requirements if I read that correctly.

Yeah I think its needed by https://github.com/thejcannon/darglint/blob/fd37f93b081348b6f9255d3d57f75e5d88c109a4/pyproject.toml#L40

Yeah, that's a good idea to try out.

Ubuntu 20 64bit

Arm or x86?

95% sure x86

Then I'm stumped, I'm also x84 64 bit and my test was with 3.8

I just bumped

pyproject.toml

on that branch. lets see what happens

The more data you can get from the CI machine the better. Flying blind is flying blind.

Newer

pyproject.toml

worked