Upstream here. If there's anything we can do to make your life easier, please let us know!
We only list known compatible versions in setup.py as we'd like to avoid running around with the fire extinguisher every time one of our dependencies publishes an backwards-incompatible release. We had too many cases where $dependency broke `pip install mitmproxy` and this seems to be the best way to avoid this. I am not very familiar with Debian packaging policies, so I don't know what's the best way to handle this here. We're usually compatible with the most recent version of every dependency at release time and we do track our dependencies on master quite closely: https://requires.io/github/mitmproxy/mitmproxy/requirements/?branch=master Best, Max
