---
tags: NumPy, triage
---

# 2025-12-10 NumPy triage meeting

- Time: 17:00 (6 pm) UTC
- Join via Zoom: https://numfocus-org.zoom.us/j/82096749952?pwd=MW9oUmtKQ1c3a2gydGk1RTdYUUVXZz09 (To dial in, find your local number: https://numfocus-org.zoom.us/u/kjGWtVx5y)
- [NumPy community events calendar](https://scientific-python.org/calendars)
- [Triage meetings notes archive](https://github.com/numpy/archive/tree/master/triage_meetings)
- [Community meetings notes archive](https://github.com/numpy/archive/tree/main/community_meetings) and [new meetings agenda](https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg)
- [Documentation team meetings notes archive](https://github.com/numpy/archive/tree/main/docs_team_meetings)

**Code of Conduct**
All attendees of NumPy community events must adhere to the NumPy Code of Conduct (https://numpy.org/code-of-conduct/).
If you see violations, take a screenshot, intervene in a respectful manner, and report it to the CoC Committee via email. For more information, refer to the Reporting Guidelines section on https://numpy.org/code-of-conduct/.

**Present**: Joren, Tyler, Chuck, Sam, Sayed, Matti, Manaas, Inessa, Amelia, Sebastian, Nathan, Evgeni

## Follow up from previous meetings/discussions
- ADD GH issue or PR for the followup

- Would at least need some rules to filter very old issues, but in case someone likes it: https://numpy.triage-party.mriduls.com/s/home

## New topics

- (mattip) C++ standards: how deep into C++ features do we want to go:
- Apparently the ship has sailed for templating, but we should try to limit their use to what we need
- We need to capture exceptions if we are using the C++ runtime
- We would like to try to standardize around a set of built-in dtype traits.
- We should not go further than c++-17

- Linalg `eig` always return complex? https://github.com/numpy/numpy/pull/30411

- F2py intent inout fix: https://github.com/numpy/numpy/pull/29929
- Two options:
- Cast at least some dtypes if mismatch (with copy). Forgiving, but behavior changes subtly (previously a different dtype was returned).
- Just refuse (raise error)

## Action items

- Any other pending deprecations like https://github.com/numpy/numpy/pull/30282 ?
- Nope; maybe ping Pieter Eendenbak

- Let's try to block out some time in the next meeting to go through PRs with the ENH label (there are around 100!) to try to close a bunch of them.

## Backlog

* [PRs and issues labelled with "triage review"](https://github.com/numpy/numpy/labels/triage%20review)
* https://github.com/numpy/numpy/pull/29638
* https://github.com/numpy/numpy/pull/19550
* https://github.com/numpy/numpy/pull/30361
* [Open PRs - ](https://github.com/numpy/numpy/pulls)- aim to keep below 150
* [Open PRs from first-time contributors](https://github.com/orgs/numpy/projects/5)
* [Inactive PRs](https://github.com/orgs/numpy/projects/6)

---

### Let's connect and keep the conversation going!
Join the NumPy contributor community **Slack workspace**: https://join.slack.com/t/numpy-team/shared_invite/zt-1gokbq56s-bvEpo10Ef7aHbVtVFeZv2w

Sign up to the NumPy **mailing list**: [https://mail.python.org/mailman/listinfo/numpy-discussion](https://mail.python.org/mailman/listinfo/numpy-discussion)

Subscribe to the NumPy **YouTube** channel: https://www.youtube.com/c/NumPy_team

Follow us on **LinkedIn**: https://www.linkedin.com/company/numpy/

#### Presentation topics for NumPy Newcomers’ Hour
To suggest a topic for future presentations, please leave a comment in this tracking issue: https://github.com/numpy/archive/issues/58.

---

Remember to archive this file by committing it to [github.com/numpy/archive/triage_meetings](https://github.com/numpy/archive/tree/main/triage_meetings)