Mailman 3 August 2018 - NumPy-Discussion

pytest, fixture and parametrize
by Charles R Harris 10 Aug '18

10 Aug '18

Hi All, I'm writing some tests and would like to come to a common understanding as to whether we are should use pytest fixtures and parametrized classes and functions. The immediate problem is testing over all types that should be supported, which something we should to much more of and is most easily achieved using one of those pytest tools. The advantage is code clarity and more informative error messages, the disadvantage is being dependent on pytest as unittest does not support that functionality. Thoughts? Chuck

11 12

Adoption of a Code of Conduct
by Stefan van der Walt 04 Aug '18

04 Aug '18

Hi everyone, A while ago, SciPy (the library) adopted its Code of Conduct: https://docs.scipy.org/doc/scipy/reference/dev/conduct/code_of_conduct.html We worked hard to make that document friendly, while at the same time stating clearly the kinds of behavior that would and would not be tolerated. I propose that we adopt the SciPy code of conduct for NumPy as well. It is a good way to signal to newcomers that this is a community that cares about how people are treated. And I think we should do anything in our power to make NumPy as attractive as possible! If we adopt this document as policy, we will need to select a Code of Conduct committee, to whom potential transgressions can be reported. The individuals doing this for SciPy may very well be happy to do the same for NumPy, but the community should decide whom will best serve those roles. Let me know your thoughts. Thanks! Stéfan

20 51

Roadmap proposal, v3
by Stefan van der Walt 02 Aug '18

02 Aug '18

Hi everyone, Please take a look at the latest roadmap proposal: https://github.com/numpy/numpy/pull/11611 This is a living document, so can easily be modified in the future, but we'd like to get in place a document that corresponds fairly closely with current community priorities. Best regards, Stéfan

7 11