[Feature request] Add an explicit manylinux wheel build for Python 3.6 just like there is for Python 2.7

[wagmiwiz]

When deploying Python projects to AWS Lambda, the only two supported Python environments are 2.7 and 3.6

Lambda like Zappa use manylinux versions for binary packages wherever possible during deploy time. They do this by searching for the correct file on PyPi. For example, if using python 2.7 and cryptography 2.3.1 they would find cryptography-2.3.1-cp27-cp27mu-manylinux1_x86_64.whl (which does exist in PyPi).

Given there is now a build step that publishes cp27-cp27m(u) for manylinux wheels, could the same be done for cp36? I know there is a build that generates one for abi for Python 3.4, i.e. cryptography-2.3.1-cp34-abi3-manylinux1_x86_64.whl , but this would require doing a non-standard search for lower python versions when the norm for all other PyPi packages is that versions are explicitly built.

Or perhaps I am missing something? :)

I am happy to give this a go if there is no reason why it should not be done.

[reaperhulk]

cryptography ships an abi3 wheel for macOS and linux, which is compatible with 3.4+ (including 3.7) and doesn't need a 3.7 specific wheel. pip already handles this automatically but it appears tools like zappa (and pex, see #4404) do not understand abi3 yet. You should open an issue there to get them to update their search algorithms (here is pip's current pep425 tag setup: https://github.com/pypa/pip/blob/master/src/pip/_internal/pep425tags.py).