Build wheels using cibuildwheel

[davidbrochart]

No description provided.

[davidbrochart]

@dmonad @Waidhoferj I heard you had issues building wheels with maturin, it seems to work fine with this PR (which uses cibuildwheel).

[SylvainCorlay]

@dmonad it would be great if this was merged. We have been blocked on this for a few weeks already!

[dmonad]

If I understand correctly, this only builds y-py, correct? What does this action do actions/upload-artifact@v2?

The current build script releases a new y-py package on pypi using environment variables that I configured (I think it's my account). How does this script actually release the build?

[davidbrochart]

If I understand correctly, this only builds y-py, correct?

Yes.

What does this action do actions/upload-artifact@v2?

It uploads the wheels as a zip file, that you can then download by clicking artifact at the bottom of this page: https://github.com/davidbrochart/y-crdt/actions/runs/1628614117

y_py-0.2.0-cp310-cp310-macosx_10_9_x86_64.whl
y_py-0.2.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
y_py-0.2.0-cp310-cp310-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl
y_py-0.2.0-cp310-none-win_amd64.whl
y_py-0.2.0-cp37-cp37m-macosx_10_9_x86_64.whl
y_py-0.2.0-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
y_py-0.2.0-cp37-cp37m-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl
y_py-0.2.0-cp37-none-win_amd64.whl
y_py-0.2.0-cp38-cp38-macosx_10_9_x86_64.whl
y_py-0.2.0-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
y_py-0.2.0-cp38-cp38-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl
y_py-0.2.0-cp38-none-win_amd64.whl
y_py-0.2.0-cp39-cp39-macosx_10_9_x86_64.whl
y_py-0.2.0-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
y_py-0.2.0-cp39-cp39-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl
y_py-0.2.0-cp39-none-win_amd64.whl

The current build script releases a new y-py package on pypi using environment variables that I configured (I think it's my account). How does this script actually release the build?

This requires a PyPI upload token, stored in your GitHub repo's secrets as pypi_password (see https://cibuildwheel.readthedocs.io/en/stable/deliver-to-pypi/#github-actions).
Do you want me to include this step?

[davidbrochart]

I just added the "Publish wheels to PyPI" step. It uses the same secrets that you have in main.yml (secrets.PYPI_USERNAME and secrets.PYPI_PASSWORD), and it is triggered when you push a tag.

[davidbrochart]

I removed the PyPI publishing for now, I will try it out with a dummy PyPI project.

[davidbrochart]

I just tested publishing on PyPI in this branch: https://github.com/davidbrochart/y-crdt/tree/test_pypi
It works, see the yy-py project: https://pypi.org/project/yy-py/0.2.2/#files
I installed it on my Linux machine with pip install yy-py and could import y_py successfully.
I'll push the changes here.

[davidbrochart]

@dmonad OK to merge?

[Waidhoferj]

I'm all for it 👍