tweak to upload existing build wheels with twine

Ultimately supporting #120, would it be possible to tweak your travis scripts to upload the compiled wheel to pypi instead of just the source package? I can get down to almost no build (e.g. not installing gcc or others) by using a conda docker image and then installing ffmpeg, av, and netifaces through one of their repos (happy to share this simple formula as well), but without a compiled aiortc wheel, it’s still a bit of pain.

I use a different CI/CD, but here are the few changes that appear to be required for travis.

1. Looking at this line where travis scripts are building the library …
2. Update to include bdist_wheel next to “sdist” in the above file/line
3. I don’t think so, but you may need to duplicate this environment either to include this as another build (e.g. if you want to keep source and binary separate).

While I don’t have the full travis environment to test myself, I’m happy to experiment with changes for this issue if you need it.

[jlaine]

PyAV 8.0.0 is now available in the form of binary wheels on PyPI, and so is aiortc 0.9.28!

[filips123]

You should really provide pre-built wheels on PyPI.

Building on Windows requires VS Build Tools which are very heavy and can take some time. Pre-built wheels would make installation easier and faster.

You should build and release wheels automatically with CI. Most CI providers support this, and there are also already systems that can automate building for multiple platforms.