amplify-cli: Problem with pipenv when deploying

Seems to work when i remove the

src = {editable = true, path = "./src"}

line in the Pipfile? The lambda seems to still work so I’m not sure why you have that in there since you copy all the files anyway? Also, when setting up a trigger from an s3 bucket there is no choice between Nodejs and Python? I’m getting the impression that python was an afterthought…

I also got a pipenv problem again; just to record, the exact issue was:

FileNotFoundError: [Errno 2] No such file or directory: ‘[path]/[lambda_function_virtual_env]/bin/python’ 🛑 Failed to install dependencies in [path_to_root]/amplify/backend/function/[lambda_function_name]: Error: Command failed with exit code 1: pipenv install

but the amplify pull and then push didn’t work this time. My steps to resolve this time were: cd [path_to_root]/amplify/backend/function/[lambda_function_name] pipenv --rm pipenv install (then I got an error about a version of Python wasn’t installed, so I did brew install python@[version#]) pipenv --python /usr/local/opt/python@[version#]/bin/python[version#] install cd [path_to_root] amplify push

not sure how this all happened, but hopefully someone else might find this useful.

I’ve just had this issue when trying to add a dependency to an an existing lambda editing the Pipfile. In my case could not trigger the mock of the function locally.

After getting arround thinking that the problem was my docker setup for this, found out that the problem is the auto-generated setup.py file which is not compatible with pipenv and wheel problem (python 3.8 in my case).

for the ones that know python more than me, the previous error is easy, but was not my case. In my case had to dig up the documentation to find out how the “src-layout” was supposed to work.

To solve this I’ve set the setup.py file

from setuptools import setup, find_packages

setup(
    name='src',
    version='1.0',
    packages=find_packages(where="src", exclude="index")
)

and violá… issue fixed!

Hope this prevent someone else the trouble of hours frustration.

Might be that with this issue we got a better messaging next time: https://github.com/pypa/pipenv/issues/5155

Is there any update on this?

Also, I’m getting this error when the CI tries to build the project

2022-03-10T03:43:18.568Z [INFO]: python3 found but version Python 3.7.10 is less than the minimum required version.
                                 You must have python >= 3.8 installed and available on your PATH as "python3" or "python". It can be installed from https://www.python.org/downloads
                                 You must have pipenv installed and available on your PATH as "pipenv". It can be installed by running "pip3 install --user pipenv".
                                 You must have virtualenv installed and available on your PATH as "venv". It can be installed by running "pip3 install venv".

Wrong version of python?!

fucking disgracful how AWS support does not do anything with this shitty python support, I recommend posting these issues on Linkedin and tagging AWS

Hi @esteban-serfe , the python issue is solved now. I just reinstalled the pipenv pip3 install --user pipenv in my root App directory.

Unfortunately my knowhow on python on windows is limited. Sounds like the src dependency is not been able to be installed. Is that the first or the last dependency on the packages section?

Usually I delete the virtualenv for that labda and the install process start again without issue. Sorry for not been able to help more here, but will be nice to have your solution in this case (if you find it)

I’m still having issues on auto deploy with CI/CD. It gets through most of the backend build steps but then it gets to pipenv install and it fails. I’m using Python 3.11 and my build settings file looks like:

version: 1
backend:
  phases:
    preBuild:
      commands:
        - export BASE_PATH=$(pwd)
        - yum install -y gcc openssl-devel bzip2-devel libffi-devel python3.11-pip
        - cd /opt && wget https://www.python.org/ftp/python/3.11.1/Python-3.11.1.tgz
        - cd /opt && tar xzf Python-3.11.1.tgz
        - cd /opt/Python-3.11.1 && ./configure --enable-optimizations
        - cd /opt/Python-3.11.1 && make altinstall
        - pip3.11 install --user pipenv
        - ln -fs /usr/local/bin/python3.11 /usr/bin/python3
        - ln -fs /usr/local/bin/pip3.11 /usr/bin/pip3
        - cd $BASE_PATH
    build:
      commands:
        - amplifyPush --simple
frontend:
  phases:
    preBuild:
      commands:
        - npm ci
    build:
      commands:
        - npm run build
  artifacts:
    baseDirectory: build
    files:
      - '**/*'
  cache:
    paths:
      - node_modules/**/*

thanks @josefaidt I rebuilt the project from scratch and it seems to have righted itself. I;ll have a look into the build spec. Thanks!