owned this note changed 4 days ago
Linked with GitHub

2025-02-12 NumPy community meeting

Code of Conduct
The NumPy Steering Council has made a strong commitment to creating an open, inclusive, and positive community.
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: Inessa, Chuck, Joren, Tyler Reddy, Riley Rockwell, Maanas Arora

Follow-up from the last meeting / discussions

  • Petr asked if we want to write a PEP about allowing custom DType definitions in the buffer protocol format (by abusing/etending format):

    • Yes, Sebastian and Nathan would want to but have to see when time comes around.
  • Setting up CI for windows arm may be possible now.

    • flang is available for openblas and f2py tests
  • A few new mypy only issues: redirected to MyPy.

  • Shape type meeting summary (there are PEP drafts around that, but it is still in an early phase, with two approaches and neither were convincing to Eric Traut).

  • New repo to develop typing stubs outside of NumPy: https://github.com/jorenham/numtype

    • move to numpy GitHub org at some point
    • We should look into names e.g. numpy-stubs and liberate the project on PyPI (since it seems reserved, potentially by us).

New topics

  • Should we really backport typing stub so much?
    • Sebastian: I feel it is a bit unnecessary, it seems more like a new feature, even if it is "just stubs". But I don't really think that it matters if it is just stubs. In general, I think backports are needed for regressions, or bad bugs, or trivial fixes; although not if the change might itself cause regressions.
    • Chuck: let's backport everything (typing improvements and fixes for free threaded Python). This will allow users test the new features and give us feedback.
  • mypy is working on addressing the issues affecting NumPy: https://github.com/python/mypy/issues/18343#issuecomment-2654371583

Let's connect and keep the conversation going!

Please enquire in a meeting or via email how to join the NumPy contributor community on Slack.

Sign up to the NumPy mailing list: 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/


Remember to archive this file by committing it to github.com/numpy/archive/community_meetings

Select a repo