| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Implemented review feedbacks #14961 | Sanjeev Kumar | 2019-12-05 | 1 | -12/+23 |
| | | |||||
| * | Added documentation in methods | Sanjeev Kumar | 2019-12-05 | 1 | -23/+207 |
| | | |||||
| * | Fix typos | Brian Wignall | 2019-11-25 | 1 | -2/+2 |
| | | |||||
| * | MAINT: remove deprecation warnings | mattip | 2019-11-22 | 1 | -4/+4 |
| | | |||||
| * | MAINT: fixes from review | mattip | 2019-11-18 | 1 | -2/+2 |
| | | |||||
| * | MAINT: fixes from review | mattip | 2019-11-16 | 1 | -6/+17 |
| | | |||||
| * | MAINT: pep8, remove checks of *.py files from --rst check | mattip | 2019-11-01 | 1 | -9/+10 |
| | | |||||
| * | MAINT: fixes from review | mattip | 2019-10-31 | 1 | -12/+27 |
| | | |||||
| * | TST: changes from review | mattip | 2019-10-17 | 1 | -27/+21 |
| | | |||||
| * | TST: run refguide-check on rst files in doc/* | mattip | 2019-10-17 | 1 | -70/+148 |
| | | |||||
| * | DOC: Change random to uninitialized and unpredictable in empty and ↵ | Kexuan Sun | 2019-06-15 | 1 | -1/+2 |
| | | | | | | | empty_like (#13771) * DOC: Change "random" to "uninitialized" in doctests | ||||
| * | DOC: fixes from review | mattip | 2019-02-28 | 1 | -1/+1 |
| | | |||||
| * | TEST: activate doctests on doc.structured_arrays, fix for pure doc module | mattip | 2019-01-14 | 1 | -1/+5 |
| | | |||||
| * | ENH: add "max difference" messages to np.testing.assert_array_equal (#12591) | Stephan Hoyer | 2019-01-01 | 1 | -0/+1 |
| | | | | | | | | | | | | | | | | | | | | | | | Example behavior: >>> x = np.array([1, 2, 3]) >>> y = np.array([1, 2, 3.0001]) >>> np.testing.assert_allclose(x, y) AssertionError: Not equal to tolerance rtol=1e-07, atol=0 Mismatch: 33.3% Max absolute difference: 0.0001 Max relative difference: 3.33322223e-05 x: array([1, 2, 3]) y: array([1. , 2. , 3.0001]) Motivation: when writing numerical algorithms, I frequently find myself experimenting to pick the right value of `atol` and `rtol` for `np.testing.assert_allclose()`. If I make the tolerance too generous, I risk missing regressions in accuracy, so I usually try to pick the smallest values for which tests pass. This change immediately reveals appropriate values to use for these parameters, so I don't need to guess and check. | ||||
| * | MAINT: include recfunctions module | Tyler Reddy | 2018-12-14 | 1 | -0/+1 |
| | | | | | | | | | | * added lib.recfunctions to refguide PUBLIC_SUBMODULES, as the doctests were otherwise not getting executed * fixed a failing doctest in recfunctions after above activation | ||||
| * | TST, DOC: enable refguide_check | Tyler Reddy | 2018-12-14 | 1 | -0/+951 |
| * ported the refguide_check module from SciPy for usage in NumPy docstring execution/ verification; added the refguide_check run to Azure Mac OS CI * adjusted NumPy docstrings such that refguide_check passes | |||||
 |
index : delta/python-packages/numpy.git | |
| github.com: numpy/numpy.git |
| summaryrefslogtreecommitdiff |