We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
1 parent 6c79e97 commit 8c671cbCopy full SHA for 8c671cb
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.
126
What to do here depends on your release frequency. Given that NumPy releases
127
come in a 6-monthly cadence and that features that get deprecated in NumPy
128
should stay around for another two releases, a good upper bound is
129
-``<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
130
already-released NumPy. This is safe to do if you release at least once a year.
131
If your own releases are much less frequent, you may set the upper bound a
132
little further into the future - this is a trade-off between a future NumPy
0 commit comments