AWS Lambda now has a Python 3.6 runtime. I tried switching my runtime to python3.6 but my functions are failing due to packaging-related errors (module initialization error: psycopg2 must be installed.), so I'd imagine some action needs to be taken here to support this.

I took a look at the source and it looks like pip is being invoked from the path, so I tried activating a venv with python3 -m venv venv; venv/bin/activate and then invoking sls deploy, but I got the same result. I'm not sure that the pip version used matters, when it's going to a specified path anyway, but perhaps it does?