You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would it be possible to upload a wheel distribution to PyPI? The latest version on PyPI, 3.1.0, only has a source distribution.
Having a wheel uploaded would help users in several different ways:
It would slightly speed up installs, since the wheel can just be extracted by pip instead of running through a build and then install step
It would avoid some of the issues with the deprecation of setup.py and PEP 517, since if the package has a wheel, then pip won't attempt to build and install it from source
It would help users working in more exotic environments, such as ones that build in sandboxed or containerized environments, where you cannot rely on build tools (e.g. setuptools or wheel) to be available at package installation time. This is common in systems like Bazel or Nix, which keep track of all input and output files of a build and try to minimize unnecessary dependencies in order to have hermetic and/or reproducible builds.
It seems like the work to build wheels and even update the upload-to-PyPI automation was already done in #125, so I think this would just be as easy as cutting a new release and running that automation.
If you didn't want to release a new version, then it should also be possible to retroactively upload a wheel for an existing versions. This should be as easy as running python setup.py bdist_wheel on the 3.1.0 version of the source code and then uploading the built wheel to PyPI for the existing version.
I really appreciate this library, so please let me know if there's anything I could do to help with this.
The text was updated successfully, but these errors were encountered:
Would it be possible to upload a wheel distribution to PyPI? The latest version on PyPI, 3.1.0, only has a source distribution.
Having a wheel uploaded would help users in several different ways:
setuptools
orwheel
) to be available at package installation time. This is common in systems like Bazel or Nix, which keep track of all input and output files of a build and try to minimize unnecessary dependencies in order to have hermetic and/or reproducible builds.It seems like the work to build wheels and even update the upload-to-PyPI automation was already done in #125, so I think this would just be as easy as cutting a new release and running that automation.
If you didn't want to release a new version, then it should also be possible to retroactively upload a wheel for an existing versions. This should be as easy as running
python setup.py bdist_wheel
on the 3.1.0 version of the source code and then uploading the built wheel to PyPI for the existing version.I really appreciate this library, so please let me know if there's anything I could do to help with this.
The text was updated successfully, but these errors were encountered: