|
| 1 | +--- |
| 2 | +tags: NumPy |
| 3 | +--- |
| 4 | + |
| 5 | +# 2019-09-04 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, Tyler, Warren, ZJ, Chuck, Hameer, Matti, Stéfan, Ralf, Sebastian, Peter Bell |
| 13 | + |
| 14 | + |
| 15 | +## Follow-up from last meeting / discussions |
| 16 | +- Move multibuild to MacPython and change its name (postpone until November) |
| 17 | + - move numpy-wheels to the numpy organization |
| 18 | + - move wheel builds [to azure from appveyor](https://github.com/MacPython/numpy-wheels/pull/60) |
| 19 | + Stopped work on this until after the current release cycle |
| 20 | + Nothing has changed since last week |
| 21 | + |
| 22 | +- 1.17.1 and 1.16.5 released!! Documentation at https://numpy.org/doc not updated yet. |
| 23 | + |
| 24 | +- NumPy developer weekend: Nov 22-23. Some of the documentation team may join, we should publish the dates. Tentative agenda [here](https://hackmd.io/t06nCEAfSJ6DhPnkhlUDRg) |
| 25 | + - Also invite documentation writers that are nearby |
| 26 | + |
| 27 | +- NumPy Community Survey |
| 28 | +Volunteers for translations: |
| 29 | +Hindi - Pankaj Jangid |
| 30 | +Chinese - ZJ Poh |
| 31 | +Spanish - ? |
| 32 | +Portuguese - ? |
| 33 | +<i>(Contact Inessa if you would like to help.)</i> |
| 34 | + |
| 35 | +All NumPy community members are invited to contribute to the creation and selection of questions by submitting pull requests to github.com/numpy/numpy-surveys. |
| 36 | + |
| 37 | + |
| 38 | +# Topics |
| 39 | + |
| 40 | +- Refresh the admins of the github [numpy organization admins](https://github.com/orgs/numpy/teams/owners-legacy) |
| 41 | +- Rackspace [wheels](https://7933911d6844c6c53a7d-47bd50c35cd79bd838daf386af554a83.ssl.cf2.rackcdn.com/) and [openblas](https://3f23b170c54c2533c070-1c8a9b3114517dc5fe17b7c3f8c63a43.ssl.cf2.rackcdn.com/) uploads. |
| 42 | + - Matthew Brett has the unencrypted key. Does anyone else? |
| 43 | + - Should be part of the private repo for NumPy management. |
| 44 | + - we should upload arm and powerpc OpenBLAS to there as well (currently on DroBox since Tyler builds them) |
| 45 | +- TODO Document ownership of keys in https://gitlab.com/numpy/logistics |
| 46 | + |
| 47 | +- Our [information at nabble](http://numpy-discussion.10968.n7.nabble.com/) is outdated. They asked for names of new admins. Who should we submit? All the steering committee? |
| 48 | + - Put on Chuck, Ralf, Matti, Sebastian, Stefan |
| 49 | + |
| 50 | +- Private vs. public submodules in namespace, we're continuing to just add random public-looking things, it's a bit of a mess. What do we do? |
| 51 | + - For `numpy.random` see e.g. [gh-14360](https://github.com/numpy/numpy/pull/14360) |
| 52 | + - Another example: `dir(np.lib.mixins)` |
| 53 | + - We should add a test that hardcodes the current namespace, and will fail if anything is added without a PR. |
| 54 | + - Polynomial namespace, multiple ways of calling the poly functions; Eric Wieser has a [suggestion](https://github.com/numpy/numpy/pull/13601#issuecomment-525591808) on how to fix |
| 55 | +- TODO Follow up on surveying new public API surface in `np.random` |
| 56 | + |
| 57 | +- Open PRs, waiting for review/merge: |
| 58 | + - [NEP-31](https://github.com/numpy/numpy/pull/14389), should be merged quickly as per NEP-0 |
| 59 | + - TODO Add a sentence to NEP0 to walk back slightly the highly optimistic merge policy (we will still merge rejected NEPs, but then with the rejected status already in place) |
| 60 | + |
| 61 | +- NEP 31, for those who have read it. (Hameer) |
| 62 | + - NEP for `uarray`: [PR#14389](https://github.com/numpy/numpy/pull/14389), [mailing list thread](https://mail.python.org/pipermail/numpy-discussion/2019-September/079961.html). |
| 63 | + - Should we change the submodule? I feel since NumPy is not deeply nested, `numpy.overridable` is enough. Vendor or move to `numpy` org? |
| 64 | + - Should we change the name? `numpy.unumpy` would also be good, although a bit of a tongue twister. |
| 65 | + - Any other suggestions/discussion? |
| 66 | + |
| 67 | +- [*NEP 32: Remove the financial functions from NumPy*](https://github.com/numpy/numpy/pull/14399) has been announced on the mailing list. |
| 68 | + |
| 69 | +## Additional Details |
| 70 | + |
| 71 | +- Matti |
| 72 | + - gave a tutorial on wrapping C code at EuroScipy. Participated today in discussions on [diversity](https://hackmd.io/hLbQbLckTUal-XopUJ303Q?both) and sustainability |
| 73 | +- Sebastian |
| 74 | + - [Extensible Datatypes for NumPy](https://hackmd.io/kxuh15QGSjueEKft5SaMug) |
| 75 | + - Started (prototyping): https://github.com/seberg/numpy/pull/6 |
| 76 | + |
| 77 | +- Warren |
| 78 | + - Wrote "NEP 32: Remove the financial functions from NumPy" and announced it on the mailing list. |
| 79 | + - Learning C API for Python and NumPy custom dtypes: |
| 80 | + - Created a Python object in C as an exercise: "nannable" int32. |
| 81 | + - Working on making this into a custom NumPy dtype. |
| 82 | + |
| 83 | + |
| 84 | +--- |
| 85 | + |
| 86 | +Please remember to archive this file and commit it to github.com:bids-numpy/docs |
| 87 | + |
0 commit comments