---
# System prepended metadata

title: 'Numba Meeting: 2026-01-27'
tags: [meeting_notes]

---

# Numba Meeting: 2026-01-27

Attendees: ToddA, Swapnil, Val, Stuart, Kaustubh, Siu, Graham, Guilherme
FPOC (last week): Val
FPOC (incoming): 

NOTE: All communication is subject to the [Numba Code of Conduct](https://github.com/numba/numba-governance/blob/accepted/code-of-conduct.md).


Please refer to [this calendar](https://calendar.google.com/calendar/embed?src=5rqnddm4gjrdfjm31fsv182epk%40group.calendar.google.com) for the next meeting date.

## ~~Office hour signup~~



## Discussion

- (esc) - https://github.com/numba/numba/pull/10384
    - Do we list all Tier 2 platforms and attempt to accurately maintain this document?
    - The Q regarding `osx-64` (Intel chips, not M* series) has come up at least twice via discourse since that platform was relegated from Tier 1.
    - We can merge this, but it won't be solve the problem of people trying to install on `osx-64`.
    - Need an env variable to force building from source.
- (esc) https://github.com/numba/numba/pull/10352
    - Are we OK to just remove headers?
    - How do we move forward on this issue.
    - Graham is working on a PR
- (esc) https://numba.discourse.group/t/type-annotations-in-llvmlite/3193
    - Does anyone strongly object to attempting to add type annotations to llvmlite?
    - Controversial, not everyone is convinced
    - Quality of the contribution needs to very good
    - Public API only to reduce maintenance burden
- (swap357) Numpy2.4 support issues and release readiness.
    - PR was recently merged, a few non-breaking issues remain.
    - Needs tetsing on CUDA
    - Needs check of icelake vs. saphire-rappids
- (swap357) Should we reconsider 30 days to stale bot policy for issues ? Especially during winter-break. can we pause the bot then?
    - disable workflow via GitHub UI in future 
- (esc) https://github.com/numba/numba/pull/10386
    - Do we need to implement the full NumPy select stuff? 
    - Yes, PR was closed
- (esc) https://github.com/numba/llvmlite/issues/1389#issuecomment-3770977823
    - Do we want to support `osx-64` for another 18 months?
    - Decision has been made, we are not bringing this back


## New "Ready for Review" PRs

## 1. New Issues
- [numba#10406](https://github.com/numba/numba/issues/10406) - Proposal: Tier 1.5 support level for "emerging" platforms
  - OK
  - Will not accept anything that changes build infra massively, e.g. `vcpkg`
  - Free-threading probably OK
  - OK for Stan to propose documentation changes 
- [numba#10407](https://github.com/numba/numba/issues/10407) - [Bug] Hard-coded 32-byte alignment in BaseContext causes Segmentation Faults on s390x
  - PR available
  - Graham will review PR
  - Stuart suggests to ping @detrout from debian to cross-check 
- [numba#10408](https://github.com/numba/numba/issues/10408) - NumPy functions with no scalar support
- [numba#10412](https://github.com/numba/numba/issues/10412) - sum and np.sum() algorithm needs to catch up to improved upstream precision
  - There might be a pull-request about this somewhere, (3046?) 

### Closed Issues

## 2. New PRs
- [numba#10410](https://github.com/numba/numba/pull/10410) - Adjust preferred array alignment for s390x to 16 bytes
- [numba#10411](https://github.com/numba/numba/pull/10411) - Update actions/checkout action to v6.0.2
- [numba#10413](https://github.com/numba/numba/pull/10413) - Improve gitlog2changelog.py

### Closed PRs
- merged - [numba#10409](https://github.com/numba/numba/pull/10409) - Update actions/setup-python action to v6.2.0
- merged - [llvmlite#1394](https://github.com/numba/llvmlite/pull/1394) - chore(deps): update actions/setup-python action to v6.2.0
- merged - [llvmlite#1395](https://github.com/numba/llvmlite/pull/1395) - chore(deps): update actions/checkout action to v6.0.2
- [llvmlite#1396](https://github.com/numba/llvmlite/pull/1396) - [DONOTMERGE] Upgrade Llvmdev version to 21.1.8

(last numba: 10413; llvmlite 1396)






