Repository navigation
CI: Upload wheels to scipp pypi index - #3542
Conversation
|
In your example command, why is anaconda the |
|
Please explain this setup in the dev docs. E.g., https://scipp.github.io/development/releasing-scipp.html |
|
The order does matter, with pip |
|
The triggered did upload all the wheels to https://pypi.anaconda.org/scipp/simple/scipp ! |
|
The links all point to the latest docs. I don't think they are a big issue if they simply get overwritten. Does the action overwrite existing wheels? |
No, it will only overwrite if they had the same name but they won't as it uses the commit hash in the name. We would need to setup a cleaning action to make sure we don't keep the old wheels around. https://github.com/scientific-python/upload-nightly-action/blob/main/.github/workflows/remove-wheels.yml as an example. |
|
This looks pretty complicated. Do we really need all of this? Or is there a simple way to wipe the index every night before upload? |
|
I'm waiting for a new release upstream https://github.com/scientific-python/upload-nightly-action first before merging this. |
5 participants
We can push wheels to pypi.anaconda.org/scipp and then we can use something like:
to get nightly wheels instead of renaming built wheels and creating static urls.
We also should have something like https://github.com/scientific-python/upload-nightly-action/blob/main/.github/workflows/remove-wheels.yml to clean up old wheels, but let's test this infrastructure out first. If we are happy, we can further iterate on this :)