Pipkin says pip is missiing, should there be a check for it, first?

[brianlinuxing]

I decided use Pipkin locally (everything is running in a VM) and get it to pull over what I needed, outside of Thonny.

It nearly seems to work, except for an odd error about pip (which is installed elsewhere, but I am probably missing something)

The command executed: /home/brian/.local/bin/pipkin -v --dir /home/brian/.micropython/lib install micropython-logging

The output suggests either an error message should come up and say "this bit is missing" or have a suggested method of rectifying it:

brian@SparkyuPython3:~$ /home/brian/.local/bin/pipkin -v --dir /home/brian/.micropython/lib install micropython-logging

The output:

Starting install
Start populating venv
Using existing working environment at /home/brian/.cache/pipkin/workspaces/77b23d5cc84289b84f594d790c14a557
Received lock on the working environment
Querying site packages path for /home/brian/.cache/pipkin/workspaces/77b23d5cc84289b84f594d790c14a557
Got site packages path /home/brian/.cache/pipkin/workspaces/77b23d5cc84289b84f594d790c14a557/lib/python3.10/site-packages
Clearing /home/brian/.cache/pipkin/workspaces/77b23d5cc84289b84f594d790c14a557/lib/python3.10/site-packages
Done populating venv
Querying site packages path for /home/brian/.cache/pipkin/workspaces/77b23d5cc84289b84f594d790c14a557
Got site packages path /home/brian/.cache/pipkin/workspaces/77b23d5cc84289b84f594d790c14a557/lib/python3.10/site-packages
Using PipkinProxy at http://127.0.0.1:36628
Calling pip: /home/brian/.cache/pipkin/workspaces/77b23d5cc84289b84f594d790c14a557/bin/python3 -I -m pip --disable-pip-version-check --trusted-host 127.0.0.1 install --no-compile --use-pep517 --upgrade-strategy only-if-needed micropython-logging --index-url http://127.0.0.1:36628
/home/brian/.cache/pipkin/workspaces/77b23d5cc84289b84f594d790c14a557/bin/python3: No module named pip

I checked $PATH just in case something was missing but seems OK:
echo "${PATH//:/$'\n'}"
/usr/local/bin
/usr/bin
/bin
/usr/local/games
/usr/games
/home/brian/.local/bin

Any suggestions @aivarannamaa ?

[brianlinuxing]

This is now reference by thonny/thonny#2478 (comment)

[aivarannamaa]

Thank you for the report!

/home/brian/.cache/pipkin/workspaces/77b23d5cc84289b84f594d790c14a557/bin/python3: No module named pip

This one surprises me. At first lauch pipkin is supposed to create a venv (/home/brian/.cache/pipkin/workspaces/77b23d5cc84289b84f594d790c14a557 in your case), even if it is launched from a venv itself, and install a specific version of pip into it. For all further actions it is supposed to use the interpreter of this venv.

Can you tell me, what do you see in /home/brian/.cache/pipkin/workspaces/77b23d5cc84289b84f594d790c14a557/lib ? Does it contain python3.X/site-packages/pip ? If yes, then there is probably something in your environment, I haven't considered.

Did you install pipkin with pip install --user pipkin?

[brianlinuxing]

Thank you for the swift reply, Aivar

Answering your last question first.

1. Don't fully recall, but my command history on that particular Virtual Machine, shows:

pip3 install pipkin (from the local user, brian)

2. I did look before. I had assumed much of what you said, that it would set up an environment then execute its tasks, but I couldn't find pip in the "temp" directory, at all. (See 3 for my failed attempt afterwards)

The contents of a whereis command looks like:

whereis pip
pip: /usr/bin/pip /home/brian/.local/bin/pip /usr/share/man/man1/pip.1.gz

I am happy to run any tests you suggest, or fiddling if I mis-installed or mucked it up (which is very possible!)

3. Last week (when I had more brains) I did try and get it to reference pip elsewhere with a symbolic link but that failed as well, see below in the screenshot, see pipkin_v3

4. The contents of the directories are in the second screenshot. Nothing, see pipkin_v2

5. So I am very happy to wipe everything and re-start with any debugging techniques that you might suggest :)

[aivarannamaa]

I'm sorry for not replying earlier.

I now tried installing pipkin while not in a virtual environment, but still couldn't reproduce the issue. I'm hoping you met some glitch in an earlier version, which got your cache into bad state.

You could try following:

• wipe pipkin's cache (rm -rf ~/.cache/pipkin)
• delete any symlinks you created for pip
• uninstall pipkin
• reinstall pipkin (I just uploaded version 1.0b6)

.. and then try installing what you tried to install before.

[brianlinuxing]

Thank you for your efforts, I shall try again, on another clean test system. :)