|
| 1 | +--- |
| 2 | +tags: NumPy |
| 3 | +--- |
| 4 | + |
| 5 | +# 2019-06-19 NumPy Development Meeting |
| 6 | + |
| 7 | +- Join via Zoom at https://berkeley.zoom.us/j/762261535 |
| 8 | +- [Trello workboard](https://trello.com/b/Azg4fYZH/numpy-at-bids) |
| 9 | +- [Previous meetings](https://github.com/BIDS-numpy/docs/tree/master/status_meetings) |
| 10 | + |
| 11 | +**Present:** Sebastian, Matti, Chuck |
| 12 | + |
| 13 | +## Follow-up from last meeting / discussions |
| 14 | +- Talk for SciPy2019 |
| 15 | + - We need data to show how the grant has affected the project |
| 16 | + - Nelle responded to a private mail but has not yet provided data |
| 17 | + - Talk so far is in [the repo](https://gitlab.com/numpy/scipy2019-presentation-insidenumpy)---note that this is a private repo |
| 18 | + - Long term sustainability of development (and continued funded development) is on our mind; Tyler is heading back to Los Alamos end of this week |
| 19 | +- 1.17 release upcoming: review PRs/Issues marked with [1.17 milestone](https://github.com/numpy/numpy/milestone/62). At last count there are 9 open issues and 5 open PRs with the milestone, maybe just start bumping issues at this point |
| 20 | + - [PR #13764](https://github.com/numpy/numpy/issues/13764) should be merged, moves windll code to a `_distributor_init.py` file when using OpenBlas on Windows |
| 21 | + - 4 of the PRs have to do with random, see below. |
| 22 | + |
| 23 | +- Random generator work |
| 24 | + - How many BitGenerators to include: the general concensus is to include a minimum rather than a maximum, and to use PCG64 as the default. Matti will submitted PRs to implement this decision. |
| 25 | + - Create bitgenerator repo for the moment. |
| 26 | +- PR for SeedSequence as a way to seed the BitGenerators |
| 27 | + - Would it help for the full-time devs to submit a PR to randomgen to update it for the changes: |
| 28 | + - Base class for BitGenerator |
| 29 | + - SeedSequence |
| 30 | + |
| 31 | +- 1.18 plans: If it is a "settle down" release, how do we approach larger code changes i.e. for dtypes? |
| 32 | + |
| 33 | +## Topics |
| 34 | + |
| 35 | + |
| 36 | +## Additional Details |
| 37 | + |
| 38 | +- Matti |
| 39 | + - The windll change began a push to move OpenBLAS handling to a central pytohn-based file rather than have each CI system in MacPython/numpy-wheels have its own solution. Still thinking about how to do this cleanly. |
| 40 | + - Gave a talk at a community college's computer engineering seminar about open source, python, jupyter. |
| 41 | + - Figured out how to link to cpython documentation in sphinx: `:ref:c:member:PyTypeObject.tp_as_number` |
| 42 | + |
| 43 | +- Sebastian |
| 44 | + - Mocked up a possible approach for dtypes at: https://github.com/seberg/numpy_dtype_prototype |
| 45 | + - Maybe present it at a BOF session at SciPy (Chuck)? |
| 46 | + |
| 47 | +- Hameer |
| 48 | + - PR for NEP Template: [#13766](https://github.com/numpy/numpy/pull/13766). |
| 49 | + - Looking for feedback. |
| 50 | + |
0 commit comments