Siu Kwan Lam
Siu Kwan Lam
Tested against https://github.com/numba/numba-hatchery/pull/8/commits/a6a6eee395026bf818bf3cc8a12129e6f14c69df (3.13.0rc1 docker image) and all passing
CI passes on Python3.13 and other deps upgrade: https://github.com/numba/numba/pull/9697/files#diff-7915b9b726a397ae7ba6af7b9703633d21c031ebf21682f3ee7e6a4ec52837a5 Currently, CI relies on `pip install numpy==1.26.3` on python 3.13 until conda packages are available.
Synchronized to #9726
Azure CI config for py3.13 deferred to: https://github.com/numba/numba/pull/9697
RE: https://github.com/numba/numba/pull/9682#issuecomment-2385060109 It's coming from Scipy: ```pytb /numba/numba/__init__.py:43: UserWarning: A NumPy version >=1.22.4 and
Oldly scipy 1.12 for python3.10 incorrectly accept numpy>=1.22.3 ``` scipy 1.12.0 py310hdb2ea58_0 ---------------------------- file name : scipy-1.12.0-py310hdb2ea58_0.conda name : scipy version : 1.12.0 build : py310hdb2ea58_0 build number: 0 size...
/azp run
Azure actually passed everything. There are lingering failing states that GH is picking up from old builds.
BFID: `numba_yaml_498`
> BFID: `numba_yaml_498` almost passed (with the usual buildfarm hiccups)