-
Notifications
You must be signed in to change notification settings - Fork 88
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
DOC: tweak README #536
base: devel
Are you sure you want to change the base?
DOC: tweak README #536
Conversation
TODO: check that the links are still relevant, mention cibuildwheel, and hint that projects should use that instead. |
Should the README have a pointer to https://docs.github.com/en/actions/use-cases-and-examples/building-and-testing/building-and-testing-python#publishing-to-pypi? |
Co-authored-by: Andrew Murray <[email protected]>
Co-authored-by: Andrew Murray <[email protected]>
Maybe. I view multibuild as a wheel building tool, I am not sure deploying wheels is in its scope. I left the bit about scientific-python-nightly-wheels for historic reasons, but maybe it makes sense to mention direct publishing as well. Although that link is only for github, right? |
Co-authored-by: Andrew Murray <[email protected]>
Let's put this in as-is. There is more room for improvement if someone wants to submit another PR. |
The README for the repo only refers to travisCI and Appveyor. The github CI is much more prevalent these days. Reword the content to mention CI-specific content less. Also, the rackspace uploads are ancient history. Mention SPEC04 and scientific-python instead.