diff options
| author | Roman Yurchak <rth.yurchak@gmail.com> | 2021-03-01 13:47:02 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-03-01 13:47:02 +0100 |
| commit | 8c671cb7a2e99dbd4146a77c0e88f4d24efc911f (patch) | |
| tree | 76523d8150bc0b2a6c4fb85b933453f6225cbbcc | |
| parent | 6c79e97d7bac51adb292ce6f7d4d77376f818d52 (diff) | |
| download | numpy-8c671cb7a2e99dbd4146a77c0e88f4d24efc911f.tar.gz | |
DOC Improve formatting in the depending_on_numpy documentation (#18518)
| -rw-r--r-- | doc/source/user/depending_on_numpy.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/source/user/depending_on_numpy.rst b/doc/source/user/depending_on_numpy.rst index 4cf272d09..d8e97ef1f 100644 --- a/doc/source/user/depending_on_numpy.rst +++ b/doc/source/user/depending_on_numpy.rst @@ -126,7 +126,7 @@ released there will be no matching version of your package that works with it. What to do here depends on your release frequency. Given that NumPy releases come in a 6-monthly cadence and that features that get deprecated in NumPy should stay around for another two releases, a good upper bound is -``<1.xx+3.0`` - where ``xx`` is the minor version of the latest +``<1.(xx+3).0`` - where ``xx`` is the minor version of the latest already-released NumPy. This is safe to do if you release at least once a year. If your own releases are much less frequent, you may set the upper bound a little further into the future - this is a trade-off between a future NumPy |