No such file or directory: '.../venv/bin/python3'

[karmingc]

I was previously using circleci/python:3.8.10 and found no issues with my build, both on PRs and on main branch builds.

      - restore_cache:  # ensure this step occurs *before* installing dependencies
          key: deps9-{{ .Branch }}-{{ checksum "requirements.txt" }}
      - run:
          name: install requirements
          command: |
            python3 -m venv venv
            source venv/bin/activate
            pip install -r requirements.txt
      - save_cache:
          key: deps9-{{ .Branch }}-{{ checksum "requirements.txt" }}
          paths:
            - "venv"

As part of migrating from python 3.8 to python 3.10x on my web application, I updated to cimg/python:3.10.4 and there were no issues with PRs - the circleci went through successfully. However, once merged to main branch, it started failing with

#!/bin/bash -eo pipefail
python3 -m venv venv
source venv/bin/activate
pip install -r requirements.txt

Error: [Errno 2] No such file or directory: '/home/circleci/<project name>/venv/bin/python3'

Exited with code exit status 1
CircleCI received exit code 1

I'm suspecting some issues with caches, but i'm unsure how to resolve.

When i tried to SSH into the PR, i can see python3 in blue cyan, which i'm assuming is a symlink.

However, once merged, python3 is in red...

Any ideas?

[karmingc]

@FelicianoTech do you mind taking a look?

[karmingc]

oddly, it does seem to be re-appearing anymore... closing this issue.

[merwok]

We’ve had this issue regularly and I diagnosed it today as this one.

We depend on cimg/python:3.10, tox ends up creating a patch-version-specific symlink like ~/.pyenv/versions/3.10.11/bin/python, we cache the virtualenv, then on a release day the cache is restored and the symlink broken.

For an X.Y version, I would not mind if the symlink was to X.Y python, meaning patch updates happen without notice.
Or if you tell me that I should use X.Y.Z today with dependabot to get updates, that would work for me too!

[shaunagm]

We've been having this issue for ages too (at least, I think it's this issue). Is there an easier way to fix this problem then doing a separate commit to update the cache keys every time?