Can you explain a little more what the concrete upside is here? For context: I've never built a phone app, let alone tried to consume a ios or android wheel.
How would a developer targeting ios or android consume the PyPI wheels and why is what they currently do a big pain for downstream? Building new wheels is a concrete ongoing commitment from us. One thing I've noticed is that ths ios builds in CI are often blocked on available Mac GitHub runners but that's a very minor issue. Still, it'd be nice to figure out how to run fewer Mac CI jobs or exploit parallelism more efficiently. On Mon, Nov 2, 2026 at 6:26 AM Malcolm Smith <[email protected]> wrote: > Hi everyone, > > As you may remember, Android and iOS support was merged into NumPy a few > months ago, and both of them were added to NEP 57 as Tier 3 platforms. As > far as I'm aware, they've both been running reliably in CI since then, so > I'd like to propose moving them to Tier 2 and releasing their wheels on > PyPI starting with NumPy 2.6 next month. > > This will allow users of Termux, Chaquopy, BeeWare and Kivy to obtain > up-to-date versions of NumPy, without each of those projects needing to > maintain their own builds as they've been doing until now. > > Let me know if you have any questions. > > Thanks, > Malcolm > _______________________________________________ > NumPy-Discussion mailing list -- [email protected] > To unsubscribe send an email to [email protected] > https://mail.python.org/mailman3//lists/numpy-discussion.python.org > Member address: [email protected] >
_______________________________________________ NumPy-Discussion mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3//lists/numpy-discussion.python.org Member address: [email protected]
