René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Dependencies aren't included in the dist/*.zip file after a build","articleBody":"Thanks for all the work that's been done on this tool and for sharing as open-source, it really looks promising.\r\n\r\nI have run `lambda build` but it doesn't appear to add any of the dependencies for my Lambda function in the resulting `dist/*.zip` file. I have a `requirements.txt` in the project directory (as described [here](https://hackersandslackers.com/improve-your-aws-lambda-workflow-with-python-lambda)) but this doesn't appear to have any effect. \r\n\r\nFor example, in the Lambda function Python file containing the handler function, I import a single package/module `abc.xyz` that is implemented in a local source folder, and I will install from there instead of from PyPI or git repositories as for more typical, non-local dependencies. This module has dependencies of its own and uses `psycopg2` to make a connection to PostgreSQL.\r\n\r\nThe `requirements.txt`:\r\n```\r\ncertifi==2020.4.5.1\r\n/home/james/git/abc\r\npsycopg2-binary==2.8.5\r\nsix==1.14.0\r\nSQLAlchemy==1.3.16\r\nSQLAlchemy-Utils==0.36.3\r\n```\r\n\r\nMy assumption was that `python-lambda` would use `pip` to somehow install all these dependency packages someplace and then add these into a `/dist/*.zip` that also includes the Lambda function Python file. Maybe there's something else required to trigger the addition of dependencies into the `/dist/*.zip` when running a build?","author":{"url":"https://github.com/monocongo","@type":"Person","name":"monocongo"},"datePublished":"2020-04-17T20:03:26.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/490/python-lambda/issues/490"}