Description
Describe the problem you are trying to solve:
The lack of a built distribution (wheel) makes it harder for tools to determine package dependencies.
As an example, if you visit https://libraries.io/pypi/google-ads the package is listed as having 0 dependencies. For comparison see https://libraries.io/pypi/pytest, where it lists the number of dependencies and links to each of them. The public BigQuery dataset also doesn't list any dependencies for this package.
This is a side effect of only a source distribution being published to PyPI. The problem is described in this blog post: Why PyPI Doesn't Know Your Projects Dependencies. In the future, it's expected that tools will be able to fetch declared dependencies from source distributions as well. However, at present, the easiest way to make metadata available is to publish a built distribution.
Describe the solution you'd like:
Publish a bdist in addition to the sdist (source distribution).
I believe this package can be published as a "pure python wheel". https://packaging.python.org/guides/distributing-packages-using-setuptools/#pure-python-wheels
Describe alternatives you've considered:
Additional context:
I work on the Cloud libraries and have been looking for dependents of google-api-core and google-auth to apply a change like the one in #473 to minimize diamond dependency conflicts. The primary way I've been finding dependents is through the PyPI BigQuery dataset.