pull_requests: 1844532658
This data as json
| id | node_id | number | state | locked | title | user | body | created_at | updated_at | closed_at | merged_at | merge_commit_sha | assignee | milestone | draft | head | base | author_association | auto_merge | repo | url | merged_by |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1844532658 | PR_kwDOAMm_X85t8VWy | 8978 | closed | 0 | more engine environment tricks in preparation for `numpy>=2` | 14808389 | Turns out `pydap` also needs to build with `numpy>=2`. Until it does, we should remove it from the upstream-dev environment. Also, `numcodecs` build-depends on `setuptools-scm`. And finally, the `h5py` nightlies might support `numpy>=2` (`h5py>=3.11` supposedly is `numpy>=2` compatible), so once again I'll try and see if CI passes. - [x] towards #8844 | 2024-04-28T17:54:38Z | 2024-04-29T14:56:22Z | 2024-04-29T14:56:21Z | 2024-04-29T14:56:21Z | a05fe82a16a29234d9e3c6f1cab550e5e7a34034 | 0 | 4a222d97ad8130dd3dc143980a024eccc6c40010 | 36a9cbc483208d7884a94abce5abdd0b48155297 | MEMBER | 13221727 | https://github.com/pydata/xarray/pull/8978 |
Links from other tables
- 2 rows from pull_requests_id in labels_pull_requests