I have been using this package as part of a Docker build. But for local development on Windows, we are having issues, as we do not have access to C++ build tools. Hence, it would be of value to have precompiled binaries for Windows as well.
I see that you have precompiled binaries for Python 3.6-3.12 for manylinux here, but could you add the same for Windows.
You likely do not have this, as you are running the builds locally on a Linux desktop. But I would suggest just making a GitHub Actions workflow for this.
If you want, I can draft up a PR for this, which produces the binaries for Windows and Linux.
cc: @coleifer
EDIT: It would even be possible to use twine to push built binaries to PyPI directly, if of interest. But thats up to you what you want. Alternatively, just storing the precompiled binaries are Artifacts is a simple way to solve this, but then you would need to manually download these and run these twine command locally.
I have been using this package as part of a Docker build. But for local development on Windows, we are having issues, as we do not have access to C++ build tools. Hence, it would be of value to have precompiled binaries for Windows as well.
I see that you have precompiled binaries for Python 3.6-3.12 for manylinux here, but could you add the same for Windows.
You likely do not have this, as you are running the builds locally on a Linux desktop. But I would suggest just making a GitHub Actions workflow for this.
If you want, I can draft up a PR for this, which produces the binaries for Windows and Linux.
cc: @coleifer
EDIT: It would even be possible to use
twine
to push built binaries to PyPI directly, if of interest. But thats up to you what you want. Alternatively, just storing the precompiled binaries are Artifacts is a simple way to solve this, but then you would need to manually download these and run thesetwine
command locally.