👋 I’m new to

pants

and giving it a test to see if it’ll work for our organisation. When generating the lockfiles or installing I get the standard pip 128 error that it can’t

git clone

and there’s no prompt to enter github username and password. I’ve tried the following: 1.

git credential store

to store the token 2. Changing the url in the git config to use the token directly:

git config --global url."https://${GITHUB_TOKEN}@github.com/".insteadOf "<https://github.com/>"

Both of these methods work fine for

git clone …

or

pip install …

but not with

pants

😕 How does

pants

interact with

pip

and

git

? Is there a setting I can change to allow it to use either of these, some thing else entirely or supply a token? For note the lines in the

requirements.txt

look like

PACKAGE_NAME@ git+<https://github.com/ORG/REPO.git@TAG>

I feel like pants will have to store these credentials somewhere inside lockfile which doesn’t sound great.

Easy way is to force everyone to use SSH 🙂

Do you know how

pants

interacts with

pip

/

git

. Does it sandbox them from the user’s configs?

Let’s wait for someone from core pants team to further help you. This is now beyond my knowledge. If you want dig inside the source code, here is the one for generating the lockfile https://github.com/pantsbuild/pants/blob/main/src/python/pants/backend/python/goals/lockfile.py

Note that I am no pex expert, but my other guess would be pex just fetches the local copy/cache of these dependencies. So I would completely uninstall it and then try generating the lockfile?

Same technique works for Docker auth and ... a few other things presently, more in the future.

@quiet-dog-11469 if you want to whac the mole in the name of incremental progress, definitely submit a PR: https://github.com/pantsbuild/pants/blob/main/docs/markdown/Python/python/python-third-party-dependencies.md#version-control-requirements It's great to get the wording fresh off the painful experience, it's more likely to really address the confusion frame.