Create wheel package of comtypes

[nanonyme]

Split from #216

Currently new pip is forced to whenever installing this package to first locally create a wheel, then install it. We should be creating and publishing universal wheels. https://packaging.python.org/guides/distributing-packages-using-setuptools/#universal-wheels

[junkmd]

This is related to #228.

I am thinking be started working on this after Py3.11 first release.

Assumed first changes

comtypes/setup.py

Lines 7 to 11 in cc9a013

	from distutils.core import Command
	from distutils.command.install import install
	from setuptools import setup
	from distutils.command.build_py import build_py

↓

from setuptools import Command, setup
from setuptools.command.install import install
from setuptools.command.build_py import build_py

[junkmd]

It would be good to work on this issue at the time of dropping Python 2.7 from support.

(related to #392)

[junkmd]

NOTE: this is related to #394.

[vasily-v-ryabov]

Current releases (including 1.2.1, of course) have universal wheels already. Is this issue still relevant or should be closed?

[nanonyme]

You're right, this is done.

[junkmd]

I recognize a package as a universal wheel available package if it has a .whl file in the Built Distribution section of https://pypi.org/project/NAME/#files.

• For example, pyyaml, which is a green package at https://pythonwheels.com/, has Built Distributions, while pyspark, which is a white package, does not have a Built Distribution.

https://pypi.org/project/comtypes/#files is satisfied the condition.

[nanonyme]

@junkmd it is not possible for projects with Python C extensions to have universal wheels. This includes pyyaml. That kind of projects have to build a per-platform wheel for all targets. Comtypes has no C extensions hence why it's possible here. Your definition for universal wheel is wrong.

[junkmd]

Thank you for bringing this to my attention.

I misunderstood the term of "universal wheels".
Upon your clarification, I checked and realized that the definition is documented at https://packaging.python.org/en/latest/guides/distributing-packages-using-setuptools/#wheels

Having removed the part that I misunderstood, and what I essentially wanted to tell is "It is a wheel available package if it has one or more .whl files in the Built Distribution section of https://pypi.org/project/NAME/#files".

(I just mentioned pyyaml as an example of a package for which wheel is available.)

Thank you.