I personally prefer using the travis runs since they get tested, even
with the additional maintenance burden of requesting travis credits when
they run out. It is good to know there is another option.
Matti
On 7/8/22 09:15, Andrew Nelson wrote:
At the moment Linux aarch64 wheels are being made in a TravisCI job.
I've been experimenting recently about making scipy wheels for that
target on Github Actions. cibuildwheel + github actions does quite
well for that purpose. It takes around 2 hours for scipy wheels to be
created (but not tested). I would expect numpy wheels to take less
time to build.
I think it would be a relatively minor modification of the
.github/workflows/wheels script.
cheers,
Andrew.
--
_____________________________________
Dr. Andrew Nelson
_____________________________________
_______________________________________________
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: matti.pi...@gmail.com
_______________________________________________
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: arch...@mail-archive.com
