Maybe this is just me missing something, but my python3.6 app zip contains a 1.5 mb future dependency, which seems to be pulled in transitively by python-jose.

My requirements.txt does not contain future, it only comes through python-jose:

boto3==1.9.15
bottle==0.12.13
python-jose==3.0.1
geopy==1.17.0
ipynb==0.5.1

It feels like future should be automatically excluded by packaging when deploying a python 3.x app. future is only meant to be used by python 2.x apps, right? I'm a python beginner, so maybe i'm missing something here. I came here because this 'unused' future library constitutes the bulk of my zip.

serverless-python-requirements already excludes boto3 from the zip, because boto3 is already present in aws. Why not excluding future when runtime: python3.6?