Shipping 3.7 wheels

[Matt Mackall]

On Thu, 2016-01-14 at 13:57 -0800, Gregory Szorc wrote:
> I /think/ packaging improvements in this cycle finally put us in position
> to offer binary wheels for Windows and OS X starting with the 3.7 release.
> (We can't offer binary wheels for Linux because, well, there still isn't a
> good answer for binary wheel compatibility on Linux.) The advantage of
> binary wheels is we can upload them to PyPI and people can `pip install
> Mercurial` and get the C extensions without needing to have a working
> compile environment.
> 
> There /might/ be an issue with the hg version string. I think wheels are
> more strict about the version format and may not like our "+1" annotation.
> This should be easily correctable with some setup.py muckery.
> 
> The bigger issue is how to produce and distribute them. I'm not sure what
> changes to the release process need to be made to support generating wheels.
> 
> What needs to be done for us to produce wheels and upload them to PyPI as
> part of the release process? 

I haven't the foggiest. I have a hacked[1] tool named twine in my release script
and that's just about the sum total of my interaction with PyPI over the past
decade.

Probably the best way forward is for someone (not it!) to make a test package on PyPI to experiment with wheel uploads and report back.

[1] The capitalization of the package on PyPI and setup.py disagree causing stock twine to puke.

-- 
Mathematics is the supreme nostalgia of our time.