|
| 1 | +--- |
| 2 | +tags: NumPy |
| 3 | +--- |
| 4 | + |
| 5 | +# 2019-09-18 NumPy Development Meeting |
| 6 | + |
| 7 | +- Time: 11am Pacific Time |
| 8 | +- Join via Zoom at https://berkeley.zoom.us/j/762261535 |
| 9 | +- [Trello workboard](https://trello.com/b/Azg4fYZH/numpy-at-bids) |
| 10 | +- [Previous meetings](https://github.com/BIDS-numpy/docs/tree/master/status_meetings) |
| 11 | + |
| 12 | +**Present:** Inessa, Hameer, Stéfan, Sebastian, Matti, Warren, Ralf, DSM |
| 13 | + |
| 14 | +## Follow-up from last meeting / discussions |
| 15 | + |
| 16 | +- In discussing build warnings, @rgommers raised the following ideas: |
| 17 | + - added a `--debug-config` option to show this output [PR 14518](https://github.com/numpy/numpy/pull/14518) |
| 18 | + - introduce a CI run that's clean with the latest GCC (existing build matrix entry could be updated). See [PR 14527](https://github.com/numpy/numpy/pull/14527) which adds -Werror to the build phase as an option to runtests |
| 19 | + - introduce a CI run that's clean on macOS with Clang (lots of warnings right now). [PR ](https://github.com/numpy/numpy/pull/14534) made a start, but clang 10 is pretty aggresive |
| 20 | + - clang on linux/windows too? |
| 21 | + |
| 22 | +# Topics |
| 23 | + |
| 24 | +- Using AVX in non-ufunc code [PR 14497](https://github.com/numpy/numpy/pull/14497) |
| 25 | + - We cannot just drop support for older CPUs |
| 26 | + - Much increased complexity |
| 27 | + - [Better PR for SIMD support](https://github.com/numpy/numpy/issues/13393) after IBM bounty |
| 28 | + |
| 29 | +- Supporting low-level cython `pxd` routines from `random` as a public API [issue 14517](https://github.com/numpy/numpy/issues/14517) |
| 30 | + - There is no plan/NEP/documented API |
| 31 | + - Get in touch with Robert to find out whether this was an intentionally supported use-case |
| 32 | + |
| 33 | +- Moving/copying all meeting notes and presentations/proposals to the numpy github organization. We should check the permissions needed for the hackmd.io integration before enabling it. Mailing list discussion. |
| 34 | + - archive repo |
| 35 | + |
| 36 | +- *NEP 32 - Remove financial functions.* There have been no more responses on the mailing list in the last week. Unless there are new objections, after the meeting Warren will send an email to the mailing list with the proposal to accept NEP 32, in accordance with ["How a NEP becomes accepted"](https://github.com/numpy/numpy/blob/master/doc/neps/nep-0000.rst#how-a-nep-becomes-accepted). |
| 37 | + - Send email to formally accept the NEP. |
| 38 | + |
| 39 | +- [Storing dtype metadata issue](https://github.com/numpy/numpy/issues/14142): |
| 40 | + - h5py new uses metadata on the dtype |
| 41 | + - Arrays saved as `npy` which have such dtypes cannot be loaded again. |
| 42 | + - Should we try to allow it? Raise an error? (what if `safe_eval` cannot load the metadata). |
| 43 | + |
| 44 | +- Reverting changes to legacy code in random [gh-14531](https://github.com/numpy/numpy/pull/14531) |
| 45 | + - we would prefer to merge Warren's PR at this point, if we get more problems we will reconsider. |
| 46 | + |
| 47 | +- [NumPy User Stories](https://mail.python.org/pipermail/numpy-discussion/2019-September/080066.html) for https://numpy.org |
| 48 | + |
| 49 | +- NumPy logo refresh |
| 50 | + - The issue about logo redesign: [numpy.org/37](https://github.com/numpy/numpy.org/issues/37) |
| 51 | + |
| 52 | + - (Matti requested that NumPy appear on it somehow) |
| 53 | + |
| 54 | +- The NumPy name is going through a trademark review and with the help of NumFocus may be trademarked. |
| 55 | + |
| 56 | +- Last year's report from the team at BIDS [is available on GitHub](https://github.com/BIDS-numpy/docs/tree/master/reports). Next report is due October. |
| 57 | + |
| 58 | +## Additional Details |
| 59 | + |
| 60 | +- Matti |
| 61 | + - adding options to distutils commands to quiet down the build_src phase (all those configure tests) and allow -Werror in the actual build |
| 62 | + - first cut at the annual report document |
| 63 | + - scipy numpy api update [PR 10840](https://github.com/scipy/scipy/pull/10840) |
| 64 | + |
| 65 | +- Sebastian |
| 66 | + - [Extensible Datatypes for NumPy](https://hackmd.io/kxuh15QGSjueEKft5SaMug) |
| 67 | + - Started (prototyping): https://github.com/seberg/numpy/pull/6 |
| 68 | + - Dtype discovery is largely working, a bit slow (still faster that current one for integers). |
| 69 | + - TODO: Add some pseudocode examples for example for how promotion will work or how dtype discovery works. |
| 70 | + |
| 71 | +- Warren |
| 72 | + - Repo for my experiments with custom dtypes using the current API is https://github.com/WarrenWeckesser/numtypes |
| 73 | + - [Repo for notes about NumPy](https://github.com/WarrenWeckesser/numpy-notes) |
| 74 | + These notes will focus on using the NumPy C API. |
| 75 | + |
| 76 | +--- |
| 77 | + |
| 78 | +Please remember to archive this file and commit it to github.com:bids-numpy/docs |
| 79 | + |
0 commit comments