|
| 1 | +# 2019-06-05 NumPy Development Meeting |
| 2 | + |
| 3 | +**Present:** Stefan, Tyler, Matti, Ralf, Chuck, Sebastian, Matthew Rocklin, Kriti, Hameer, Julian Taylor |
| 4 | + |
| 5 | + |
| 6 | +## Follow-up from last meeting / discussions |
| 7 | + |
| 8 | +## Topics |
| 9 | + |
| 10 | +- Release note management? [gh-13707](https://github.com/numpy/numpy/issues/13707) |
| 11 | + - It seems we would like to try a wiki-style release note like what scipy does. It seems to make sense to have a standard summary format for a PR that gets copy-pasted into the wiki. [skimage release notes script](https://github.com/scikit-image/scikit-image/blob/master/tools/generate_release_notes.py) There is also our changelog.py script in tools which could do more |
| 12 | +- Regression with `np.matmul` calling `__array_wrap__` with output result that is a different shape than the input. While `__array_wrap__` was not called for `a = np.matmul(df.T, df)` previously, it is not yet clear to me (mattip) how `a` turned into a `DataFrame` |
| 13 | +- Maybe `random` [needs more](https://github.com/numpy/numpy/issues/13685) work, maybe not, not clear yet. |
| 14 | + 1. Give a way to set entropy (for each program) |
| 15 | + 2. Provide better way to spawn independend streams |
| 16 | +- `rnumpy` idea: |
| 17 | + - Create seperate project, which pulls in only the core functionality into a clean namespace |
| 18 | + - Methods are a bit trickier, may be possible with fancy subclasses. |
| 19 | +- Talk for SciPy2019 |
| 20 | + - We need to finish the talk |
| 21 | + - Sebastian will do the 5-minute NumPy presentation |
| 22 | +- 1.17 release upcoming: review PRs/Issues marked with 1.17 milestone |
| 23 | +- [NEP template](https://github.com/numpy/numpy/blob/master/doc/neps/nep-template.rst): needs to be updated to encourage better justification of changes, description of scope (motivation section: what, why, for whom, how); Hameer will take a pass |
| 24 | +- should we make a table re: overhead of ufuncs, np.ones(), and so on---what's the fastest you can expect to get with modern memory, etc? |
| 25 | + |
| 26 | + |
| 27 | +## Additional Details |
| 28 | + |
| 29 | +- Tyler -- [weekly working notes](https://workflowy.com/s/june-5-2019/FPjnHcQUv3ypMimy) |
| 30 | + |
| 31 | +- Matti |
| 32 | + |
| 33 | +- Sebastian |
| 34 | + - Tried to work on refactoring ufunc resolution with the idea it may simplifier later: https://github.com/seberg/numpy/tree/no-ops-in-type-resolution (very much work in progress) |
| 35 | + - Old branch with thinking about UfuncImpl to put it out there: https://github.com/seberg/numpy/tree/ufunc-dispatch |
0 commit comments