If you prefer to avoid building psycopg2 from source, please install the PyPIįor further information please check the 'doc/src/install.rst' file (also at Or with the pg_config option in 'setup.cfg'. Python setup.py build_ext -pg-config /path/to/pg_config build.
ERROR INSTALL PYTHON ON MAC OS WITH PSYCOPG2 FULL
Please add the directoryĬontaining pg_config to the $PATH or specify the full executable path with the Pg_config is required to build psycopg2 from source. Writing manifest file '/private/var/folders/y0/qwms1cw15dz5hd87c7xgd1w40000gn/T/pip-pip-egg-info-74m7eaa4/psycopg2.egg-info/SOURCES.txt' Writing top-level names to /private/var/folders/y0/qwms1cw15dz5hd87c7xgd1w40000gn/T/pip-pip-egg-info-74m7eaa4/psycopg2.egg-info/top_level.txt Writing dependency_links to /private/var/folders/y0/qwms1cw15dz5hd87c7xgd1w40000gn/T/pip-pip-egg-info-74m7eaa4/psycopg2.egg-info/dependency_links.txt Writing /private/var/folders/y0/qwms1cw15dz5hd87c7xgd1w40000gn/T/pip-pip-egg-info-74m7eaa4/psycopg2.egg-info/PKG-INFO
ERROR INSTALL PYTHON ON MAC OS WITH PSYCOPG2 CODE
Lambda code is in the root directory +- lambda_function.py I can confirm today that the issue is fixed when I build the package from Centos 7 ( AWS AMI )īuild process pip install -r requirements.txt -target. The issue happens only when the packages are built from MAC OS. I was skeptical for depending on a third party library for my production code. If you are going to attempt to build it yourself, remember that you must build on a machine or VM with the same architecture as your target at AWS. I banged my head on this for a full day and then when i changed to 3.6, the import error just vanished.
The psycopg2 build library from jkehler/awslambda-psycopg2 was built for python 3.6 and make sure that while uploading your code to AWS lambda, select Python Runtime environment as 3.6, and it should work. Note that you don't need to build this project from scratch as the repo includes a pre-built package in the psycopg2 folder that you can simply include in your Lambda upload. One way to do this is to get them from the jkehler/awslambda-psycopg2 repo at GitHub. The AWS Lambda runtime environment doesn't include the PostgreSQL libraries so you need to include them within your AWS Lambda upload.
0 kommentar(er)
