Ensure releases on PyPI contain a wheel about abseil-py HOT 7 CLOSED

I think (not entirely sure of this) that in our case, the main advantage of a wheel is it decouples the building from the installing to certain extent. I think it would have prevented the bug a couple months ago where I used a feature in setup.py that required a newer version of setuptools, but, it turns out, some people using absl end up with a very old setuptools version from their distro. I think wheels would have prevented that.

from abseil-py.

That makes sense. Easy enough to package up as a wheel for future uploads.

from abseil-py.

What advantages does a wheel provide over sdist when there are no precompiled binary extension modules?

(anyways I think a future version of twine or pip or whatnot is supposed to auto-wheel-ify packages all the time anyways?)

from abseil-py.

from abseil-py.

I see that a new release of abseil-py has gone out without a wheel. Probably an oversight more than anything else. Would it be a good idea to setup a repeatable PyPI release process or playbook document? It can either be a README, or a Makefile, or a script or perhaps Bazel can do it (might be more complex).

from abseil-py.

Is there any chance this issue will be re-opened or addressed anytime soon?

from abseil-py.

Hi, we just pushed out a new release 0.10.0 including a wheel for Python 3. Let us know if you see any issues.

Closing.

from abseil-py.