@agriyakhetarpal now that PEP 783 for emscripten packaging is accepted does that mean that we can upload the pyodide wheels straight to PyPI?
I think that implementing this would just be a case of removing the rm line here and then making a new release:
|
# Downloads all artifacts |
|
- name: Download release artifacts |
|
uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 |
|
with: |
|
path: wheelhouse |
|
merge-multiple: true |
|
|
|
- name: Copy the PyPI files into dist |
|
# pyodide wheels cannot be uploaded to PyPI |
|
run: | |
|
mkdir dist |
|
rm wheelhouse/*pyodide*.whl |
|
cp wheelhouse/*.whl wheelhouse/*.tar.gz dist |
|
|
|
- name: Publish package on PyPI |
|
# It is recommended to pin a commit hash here for security but it |
|
# should be kept up to date. Possibly all actions and dependencies used |
|
# by the build script should be pinned... |
|
uses: pypa/gh-action-pypi-publish@cef221092ed1bacb1cc03d23a2d87d1d172e277b # v1.14.0 |
@agriyakhetarpal now that PEP 783 for emscripten packaging is accepted does that mean that we can upload the pyodide wheels straight to PyPI?
I think that implementing this would just be a case of removing the
rmline here and then making a new release:python-flint/.github/workflows/buildwheel.yml
Lines 479 to 497 in d521145