On Thu, Mar 28, 2024 at 1:28 AM Scott Guthridge < scott_guthri...@rompromity.net> wrote:
> I see that tools/wheels/upload_wheels.sh script looks for dist/*.gz first, > then wheelhouse/*.whl next and upload to the Anaconda distribution. The > only places I see this script called are in .github/workflows/wheels.yml > and ci/cirrus_wheels.yml, and in both cases appear to upload wheel files > only. > > How is the source distribution built? Does cibuildwheel also build the > SD? And how do the wheels and source distribution end up on PyPI? > The sdist is built by the release manager: https://github.com/scipy/scipy/issues/13369#issuecomment-1912185397 Wheels get downloaded from the anaconda.org staging bucket by the release manager, and then uploaded to PyPI (see https://github.com/scipy/scipy/issues/13369#issuecomment-1912185397). There is some discussion here about a trusted publishing workflow: https://github.com/scipy/scipy/issues/18869. It'd still need to go via the anaconda.org staging area though, for multiple reasons. So it'd only be a minor increase in traceability, there's still a human in the release loop. Why are you asking? Cheers, Ralf > Thanks > Scott > _______________________________________________ > SciPy-Dev mailing list -- scipy-dev@python.org > To unsubscribe send an email to scipy-dev-le...@python.org > https://mail.python.org/mailman3/lists/scipy-dev.python.org/ > Member address: ralf.gomm...@googlemail.com >
_______________________________________________ SciPy-Dev mailing list -- scipy-dev@python.org To unsubscribe send an email to scipy-dev-le...@python.org https://mail.python.org/mailman3/lists/scipy-dev.python.org/ Member address: arch...@mail-archive.com
