Why does 'sdist' does not run when scheduled? To only upload wheels to scientific-python-nightly-wheels and avoid a ~50 MB zip?

Or perhaps unhook the 'count-dists' check from the scientific-python-nightly-wheels flow?

Why does 'sdist' does not run when scheduled? To only upload wheels to scientific-python-nightly-wheels and avoid a ~50 MB zip?

It turns out I suggested it a year ago. I expect I just thought it wasn't necessary to upload it. If you'd like to though, I have no objection. I've created #9248

Or perhaps unhook the 'count-dists' check from the scientific-python-nightly-wheels flow?

All other things being equal, I think it would be better to know if we suddenly start uploading extra wheels to scientific-python-nightly-wheels.

Why does 'sdist' does not run when scheduled? To only upload wheels to scientific-python-nightly-wheels and avoid a ~50 MB zip?

It turns out I suggested it a year ago. I expect I just thought it wasn't necessary to upload it. If you'd like to though, I have no objection. I've created #9248

I checked a few others at https://anaconda.org/scientific-python-nightly-wheels/ and didn't see any sdist, so probably better not to upload a fairly large file. And the clue's in the (scientific-python-nightly-wheels) name.

Or perhaps unhook the 'count-dists' check from the scientific-python-nightly-wheels flow?

All other things being equal, I think it would be better to know if we suddenly start uploading extra wheels to scientific-python-nightly-wheels.

Agreed.

How about we use #9248 and do something like rm pillow*.tar.gz in the scientific-python-nightly-wheels-publish job just before upload?

How about we use #9248 and do something like rm pillow*.tar.gz in the scientific-python-nightly-wheels-publish job just before upload?

Sure. I've updated the PR, just changing the 'pattern' used for matching in scientific-python-nightly-wheels-publish.

Closed in favour of #9248.