Skip to content
esc edited this page Nov 8, 2023 · 1 revision

Numba Meeting: 2023-11-07

Attendees: Kaustubh, Guilherme Leobas, dipto, Gordan Jenson, val, stuart, Todd A. Anderson, brandonwillard, Siu Kwan Lam, Da Li FPOC (last week): Graham FPOC (incoming): Stuart

NOTE: All communication is subject to the Numba Code of Conduct.

Please refer to this calendar for the next meeting date.

0. Discussion

  • Winter shutdown.
    • Will be done again this year
    • Proposed period: 15th Dec - 15th Jan.
    • No FPOC / dev meetings during this period
  • Numba 1.0 question
    • Why 1.0? Could also drop the 0. and go e.g. 0.59 -> 60, 61, 62, ... with point releases, e.g 60.1, 60.2 so version is major / minor
    • Semver?
    • Date-based versioning (CalVer)
    • Discussion TBC in following weeks
  • Town crier release notes close / open avoidance
    • Potential solution inspired by NumPy: invert the label so you add it to require release notes, and at that point the check runs.
      • Resolution: try to implement this.
  • Keep Python 3.8 for 0.59?
    • Plan: drop it for 0.59
    • Add a note to the docs that we will aim to follow SPEC 0 as a minimum.
    • Siu creating issue and adding to 0.59 milestone. The issue
  • "effort" scheduling for 0.59...
    • Python 3.12 support - <1% fails, but high effort to resolve.
    • Objmode fallback removal.
      • Will be inaccessible in 0.59, removal of code paths can be done ad-hoc post-release.
    • guvectorize in jit regions?
      • Waiting on Stuart
    • anything needed for CUDA?
    • anything else?
      • pyproject.toml / setup.py discussion - conclusion: not quite able to prioritise right now due to perceived level of urgency vs resource allocation
  • https://numba.discourse.group/t/omp-use-in-manylinux-wheels/2249/2
  • OK to merge https://github.com/conda-forge/numba-feedstock/pull/128
    • Graham's error to have mentioned this - we were not being asked, the request was aimed at CF feedstock maintainers.

New "Ready for Review" PRs

1. New Issues

  • numba#9260 - Bus error: 10 when using np.linalg.solve in numba parallel=True
    • Needs debugging to check if it's an OpenBLAS or Numba issue
  • numba#9264 - Deferred types broken for jitclass
  • numba#9265 - Parfors not exporting variable sometimes
  • numba#9266 - RecursionError when sorting typed list of jitclass
  • numba#9268 - Numba compiled np.dot doesn't support type promotion of different data types
  • numba#9269 - MixedContainerUnroller pass may create variable not in scope
  • numba#9270 - Add CI tests targeting glibc=2.17
    • Unlikely that Numba can support this
    • Quite a large effort to resource for a limited time use (depending on CentOS EOL)
    • We already added run RC commit SHA on conda-forge as part of release checklist

Closed Issues

  • numba#9263 - Numba not vectorizing string array comparisons

2. New PRs

  • numba#9258 - [docs] Typo in overloading-guide.rst
  • numba#9259 - Stop type inference from indefinite retry on failed function resolution
  • numba#9261 - Workaround for tempfile.TemporaryFile hanging indefinitely on Windows
  • numba#9262 - Fix pickle RecursionError when serializing the constant part of a dynamic exception
  • numba#9267 - CUDA: Fix dropping of kernels by nvjitlink, by implementing the used list
  • llvmlite#1006 - Release Notes 0.41.1 for main
  • llvmlite#1007 - update release checklists post 0.41.1

Closed PRs

3. Short-term Roadmap

gantt: https://github.com/numba/numba/issues/8971

Clone this wiki locally