Skip to content

Conversation

@larsoner
Copy link

@larsoner larsoner commented Oct 6, 2025

Closes #64
Closes #17

Seems to be working:

https://github.com/larsoner/surfa/actions/runs/18286055605

Also enables PyPI automated publishing when a tagged release is cut

@@ -1,2 +1,7 @@
[build-system]
requires = ['setuptools', 'wheel', 'Cython>=3.0', 'numpy']
requires = ['setuptools', 'wheel', 'Cython>=3.0', 'numpy>=2']
Copy link
Author

Choose a reason for hiding this comment

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

I'd suggest updating the python min to 3.10 at the same time (3.9 is EOL Oct 30), happy to push that. Building with NumPy >= 2 is useful to ensure that code is both NumPy 1.x and 2.x compatible. But I can roll this back if needed and just make sure that cibuildwheel installs a NumPy >= 2, though it does complicate the code a bit.

@larsoner larsoner mentioned this pull request Oct 6, 2025
@larsoner
Copy link
Author

larsoner commented Oct 6, 2025

I also just saw #54... after this PR is merged, if someone bumps the version in __init__.py and creates a release on GitHub with a tag like v0.6.4 then it should land in PyPI.

@larsoner
Copy link
Author

larsoner commented Nov 26, 2025

Modified to use abi3 builds for compat with future versions of Python

EDIT: Appears to have worked: https://github.com/larsoner/surfa/actions/runs/19711633336/job/56473558969

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Distribute binary wheels? Install on windows

1 participant