Daniel Schep

Nice workaround using a great plugin!

You should keep your `requirements.txt` in the root of your service, the plugin creates the file at `.serverless/requirements.txt`.

Just thought of something it might be.. Add this to your `Dockerfile`: ```Dockerfile RUN mkdir /var/task WORKDIR /var/task ```

Ah. yeah I'll ahve to check docker-in-docker out at some point. Re this @thesmith: > Annoyingly this means you have to flip dockerizePip between deploying via CI and locally. You...

@mehdisadeghi no clue. but to be honest I wouldn't expect serverless-package-python-functions & serverless-python-requirements to work together. I don't think serverless-package-python-functions is necessary since this plugin gained the same functionality.

Sorry to get to this so late, but @bweigel and @ljofre are correct!

@IvanBernatovic because it isn't used by lambda. this plugin installs & injects(in a path that lambda will actually use) all your dependencies from your requirements file

@zakariassen do you know if `getfullargspec` also existed in older versions of python (ie: is that backwards compatible fix?)

IMO, this would best be implmented as a `secretsFile` option and then if you want per-stage files you can do `secretsFile: .serverless-secret-${opt:stage, self:provider.stage}.json`

sorry, that was a suggestion of how we might implement it. the option doesn't currently exist. If you don't mind extra secrets in your file, the work around I'd suggest...