[Bug]: Pip, pip3, & python3 shims not creating

[BradKnowles]

Description

dtvem reshim doesn't create pip, pip3, python3 shims.

Steps to Reproduce

1. Perform a user install iex "& { $(irm dtvem.io/install.ps1) } -UserInstall"
2. Install Python dtvem install python 3.14.2
3. Run python --version
4. Run pip --version

Expected Behavior

I expected pip to return a version number.

Actual Behavior

❯ pip --version
Shim invoked: pip
· 22:33:59.171 Arguments: [--version]
· 22:33:59.172 Mapped to runtime: python
· 22:33:59.172 Resolved version: 3.14.2
· 22:33:59.172 Base executable path: C:\Users\Brad\.local\share\dtvem\versions\python\3.14.2\python.exe
· 22:33:59.172 Secondary executable lookup failed: secondary executable not found: pip
✗ 'pip' is not available in Python 3.14.2
→ This shim exists because another installed Python version provides it.
→ Install 'pip' for the active version, or switch to a version that has it.
dtvem shim error: pip not available in Python 3.14.2

Operating System

Windows

dtvem Version

0.6.0

Go Version (if building from source)

No response

Which runtime is affected?

Python

Error Messages / Logs

❯ pip --version
Shim invoked: pip
· 22:33:59.171 Arguments: [--version]
· 22:33:59.172 Mapped to runtime: python
· 22:33:59.172 Resolved version: 3.14.2
· 22:33:59.172 Base executable path: C:\Users\Brad\.local\share\dtvem\versions\python\3.14.2\python.exe
· 22:33:59.172 Secondary executable lookup failed: secondary executable not found: pip
✗ 'pip' is not available in Python 3.14.2
→ This shim exists because another installed Python version provides it.
→ Install 'pip' for the active version, or switch to a version that has it.
dtvem shim error: pip not available in Python 3.14.2

Configuration

N/A

Additional Context

When I run dtvem doctor I get this...

dtvem doctor

⚠ Shim-map cache is out of sync with disk  [fixable]
  On disk, missing from cache:  pip, pip3, python3
  Run `dtvem reshim` to rebuild the cache from the installed runtimes.

✓ All configured runtimes are installed
✓ Shims directory matches installed runtimes
✓ All installed runtime versions have their executable
✓ dtvem-shim binary is present
✓ dtvem shims directory is on PATH
✓ No stale dtvem shims entries in PATH
✓ No system runtimes ahead of dtvem on PATH
✓ Only one dtvem install location holds data

⚠ 1 non-error problem(s) found across 9 check(s)

Then I return dtvem reshim (notice no pip, pip3, or python3)

→ Regenerating shims for Python...

╭────────────────────────────╮
│       Shims Created        │
│ ────────────────────────── │
│ Runtime  Shims             │
│ ────────────────────────── │
│ Python   python, pythonw   │
╰────────────────────────────╯

✓ Created 2 shims for 1 runtime(s)

Code of Conduct

• I agree to follow this project's Code of Conduct

[CalvinAllen]

Ugh, weird. This is related to something I was working on yesterday, too.

The underlying problem is that let's say, you have two installed versions of Python - 1.0.0 and 2.0.0 (for simplicity)

You install pip for 1.0.0 and get the shim, but then later in a project you default to using 2.0.0 where you DIDN'T install pip. The shim should only work for 1.0.0 since the underlying pip executable doesn't exist in the 2.0.0 install (nothing for the shim to point to).

My question here is, do you have more than one install of Python in this machine?

❯ pip --version
Shim invoked: pip

No shims were created with reshim, but yet, that error seems like it found one anyway, but just didn't map to that new version that was installed.

(Of course, there is the issue of why didn't pip install with python initially if this were all the case)

I'm struggling with the shims concept a little bit :)

[BradKnowles]

No other installs of python. I don't even have multiple runtime versions installed. I use scoop for a lot of my installs and it also uses the concept of shims, but I don't know if they implement them the same way you do. You have the added challenge of trying to have shims for multiple levels (local vs global), which I can image is challenging. I don't know enough Go to make a helpful suggestion lol.

❯ dtvem list
╭──────────────────────╮
│        Python        │
│ ──────────────────── │
│ Version  Status      │
│ ──────────────────── │
│ 3.14.2   🌐 global   │
╰──────────────────────╯

[CalvinAllen]

Gotcha, alright, so a bit more information I'm coming across - I think...

You installed 3.14.2 (according to my analysis of that package for Windows and some Q/A), Windows doesn't ship with a python3 executable, therefor, no shim. It also doesn't ship with pip directly, but that should have triggered an ensurepip, which I can only guess - failed for some reason. I did find an issue in that shims are created during an install for things like pip even if they aren't there, but a reshim does NOT do that. Kind of explains why it found a pip shim but then failed and then after a reshim it was gone (maybe).

So, I've got a couple things to look into -

1. Why did ensurepip fail
2. Fix the shim creation during an install to only be the executables present

• Of course, if ensurepip succeeds, then 2 should still create the shim

[BradKnowles]

I did try to run ensurepip manually, based on what I found in your source.

python -m ensurepip --default-pip --upgrade
Looking in links: c:\Users\Brad\AppData\Local\Temp\tmp895nbc6r
Requirement already satisfied: pip in c:\users\brad\.local\share\dtvem\versions\python\3.14.2\lib\site-packages (25.3)

[CalvinAllen]

I did try to run ensurepip manually, based on what I found in your source.

python -m ensurepip --default-pip --upgrade
Looking in links: c:\Users\Brad\AppData\Local\Temp\tmp895nbc6r
Requirement already satisfied: pip in c:\users\brad.local\share\dtvem\versions\python\3.14.2\lib\site-packages (25.3)

Ah excellent, that's the path I'm going down fixing, because the pip install is in the wrong spot based on where it goes otherwise (Scripts/pip.exe). I'm going to add a new command in there that forces the reinstall from the included wheel, which will go into the right(?) spot for the shim logic to find it.

[CalvinAllen]

@BradKnowles Alright 0.6.1 released with a couple fixes, let me know if that works better