no need for windows artifacts, we're universal

[graingert]

No description provided.

[gvanrossum]

Even if we all end up agreeing this is not needed let's not land it before 0.521 is released.

[emmatyping]

I agree with @gvanrossum. Also to be clear about the rational (for now and posterity), even though typed-ast is binary, mypy is pure Python, so platform specific wheels are not needed. It doesn't hurt to have extra wheels, but they just churn extra CI time.

(Also I asked David for your review since you put the platform build in, and wanted to make sure we werent missing anything.)

[graingert]

It doesn't hurt to have extra wheels

As you mentioned they add extra CI time, they also:

Waste of bytes on PyPI
May cause confusion, people may thing they need to build bdists for linux/mac to install mypy
May cause problems with tooling that make assumptions about universal wheels implying no other wheels.

[ddfisher]

@gvanrossum do you remember why we started having platform-specific wheels in the first place?

[gvanrossum]

@ddfisher I don't recall, I thought there was some tiny essential difference that you once explained to me (maybe it was just the filename itself). I definitely recall being surprised at first but someone (either you or Jukka) convinced me that it was necessary.

[JukkaL]

My understanding is that this commit by @ethanhs made it possible to use only a single wheel: 166d54d Previously setup.py worked differently on Windows compared to other platforms.

[emmatyping]

Ah, I believe that would do it. Before if you built on Linux it wouldn't copy the Windows script into the wheel or visa versa. Now that isnt a problem because setuptools handles the script on install I think.

[graingert]

Now that isnt a problem because setuptools handles the script on install I think.

yup

[gvanrossum]

Sorry for the delay! 0.521 has been out of the door for weeks and we haven't heard any complaints so I think we're good here.

[graingert]

Wheely great news!