Skip to content

Conversation

@astrofrog
Copy link
Contributor

As mentioned by @pllim in astropy/pytest-astropy-header#42 (comment), for the pure Python case we could just have a single job?

Comment on lines -62 to -64
- uses: actions/upload-artifact@v2
with:
path: dist/*
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be useful to keep the upload-artefact so people can download the wheel even if it isn't uploaded to PyPI? (Also, it should be easy to rebase #13 for this PR.)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Although happy to merge as I guess this is less important for pure python wheels.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

People can always build their own wheel but why would they even need it?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's right. Building locally to debug the wheels should be fine. Shall we merge this?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please do. Thanks! 😸

@ConorMacBride ConorMacBride merged commit 56abcf8 into OpenAstronomy:main Mar 11, 2022
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

Successfully merging this pull request may close these issues.

3 participants