Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Archive this repo? #2

Open
mattip opened this issue Feb 14, 2023 · 3 comments
Open

Archive this repo? #2

mattip opened this issue Feb 14, 2023 · 3 comments

Comments

@mattip
Copy link

mattip commented Feb 14, 2023

Can we archive this repo? Many of the multibuild projects under this org the MacPython org have moved to cibuildwheel, and now build via CI jobs on the main repo. Is this true of nipy?

@mattip
Copy link
Author

mattip commented Nov 9, 2023

In any case, the ANANCONDA_ORG should change to https://anaconda.org/scientific-python-nightly-wheels

if [ "schedule" == "${{ github.event_name }}" ] || [ "main" == "$BUILD_COMMIT" ]; then echo "ANACONDA_ORG=scipy-wheels-nightly" >> $GITHUB_ENV; else echo "ANACONDA_ORG=multibuild-wheels-staging" >> $GITHUB_ENV; fi

@matthew-brett
Copy link
Member

Sorry - do you mean specifically that scipy-wheels-nightly should change to scientific-python-nightly-wheels? How about multibuild-wheels-staging?

@mattip
Copy link
Author

mattip commented Nov 9, 2023

I guess it depends what you do with the staging. The nightly-wheels one is so that "nightly" builds of common libraries can be tested by download downstream libraries. If you only need the wheels to transfer them to PyPI or local testing, then I would think using a github action artifact upload would be preferable to the anaconda package hosting.

At some point I would like to shut down the scipy-wheels-nightly and multibuild-wheels-staging sites.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants