pull_requests: 1587461032
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1587461032 | PR_kwDOAMm_X85enruo | 8416 | closed | 0 | migrate the other CI to python 3.11 | 14808389 | (namely, additional CI and upstream-dev CI) `python=3.11` has been released more than a year ago and `python=3.12` is out as well, which means that it is a good idea to migrate sooner than later. Regarding `python=3.12`, usually it is `numba` that keeps us from testing on a new `python` version for some time, where `numbagg` and `sparse` are the only dependencies that would use it. Should we create a environment without those two dependencies and switch back to the normal one once `numba` supports the new python version? We still have the special environment files for `python>=3.11` because the normal ones still include `cdms2`. We deprecated that back in May – not sure which release that ended up in – but since `cdms2` will be abandoned end of this year, that's when we're free to drop support and merge both environments (though maybe we can justify dropping support earlier?) | 2023-11-05T15:26:31Z | 2024-01-03T20:17:11Z | 2023-11-17T15:27:21Z | 2023-11-17T15:27:21Z | b6eaf436f7b120f5b6b3934892061af1e9ad89fe | 0 | a5e83354ca005b4fb99e3707a71a58fbd3936373 | 22ca9ba87be071fde18a65f11f0bb4ec83188da4 | MEMBER | 13221727 | https://github.com/pydata/xarray/pull/8416 |
Links from other tables
- 3 rows from pull_requests_id in labels_pull_requests