Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,556,744
Community Members
 
Community Events
184
Community Groups

Getting a The Python interpreter can't be found error when deploying using pipeline

Hi I have started getting an error of  The Python interpreter can't be found. Below is my pipeline file

The error happens on this step - pipenv install --skip-lock --system

Any help would be amazing, as for bitbucket pipelines does it pull python from my local machine? or is this installed on a virtual machine on bitbucket side?

Screen Shot 2022-08-16 at 8.37.42 AM.png

 

 
options:

docker: true

image: python:3.8-slim

test: &test

step:

name: 'Build and Test'

script:

- echo "Your build and test goes here..."

lint: &lint

step:

name: 'Lint'

script:

- echo "Your linting goes here..."

-

push-development: &push-development

step:

name: 'Deployment to Partners'

deployment: partners

image: google/cloud-sdk:latest

trigger: 'manual'

script:

- echo ${KEY_FILE_AUTH} | base64 --decode --ignore-garbage > /tmp/gcloud-api.json

- echo ${ENV_FILE} | base64 --decode --ignore-garbage > ./api/settings/.env

- pip install pip pipenv --upgrade

- pipenv install --skip-lock --system

- pip install -r ./requirements.txt

- source ./api/settings/.env

 

1 answer

Hi, imagine my surprise when this error started appearing in my deployment (where nothing changed since the last successful one) and the first thing I find about it is an hour old post :).

The issue seems to be in the newest release of pipenv (2022.8.15), I downgraded to 2022.8.5 and it started working.

Wow ok, do you have the step command to use pipenv 2022.8.5 not really sure how to do that in bitbucket pipelines

I am not using Bitbucket, but I guess it will work if you just remove `pipenv` from:

- pip install pip pipenv --upgrade

and just add

- pip install pipenv=2022.8.5

after it in the script.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events