summaryrefslogtreecommitdiffstats
path: root/Doc/c-api/float.rst
diff options
context:
space:
mode:
authorAntonio Cuni <anto.cuni@gmail.com>2021-01-06 11:38:26 (GMT)
committerGitHub <noreply@github.com>2021-01-06 11:38:26 (GMT)
commit315fc52db17b19fe30aa9193f26adf69e18d8844 (patch)
tree90a8795e94974c667c306f8e508c4df674bfc7b8 /Doc/c-api/float.rst
parent1a9f51ed12feb4d95ad6d0faf610a030c05b9f5e (diff)
downloadcpython-315fc52db17b19fe30aa9193f26adf69e18d8844.zip
cpython-315fc52db17b19fe30aa9193f26adf69e18d8844.tar.gz
cpython-315fc52db17b19fe30aa9193f26adf69e18d8844.tar.bz2
bpo-42528: Improve the docs of most Py*_Check{,Exact} API calls (GH-23602)
I think that none of these API calls can fail, but only few of them are documented as such. Add the sentence "This function always succeeds" (which is the same already used e.g. by PyNumber_Check) to all of them.
Diffstat (limited to 'Doc/c-api/float.rst')
-rw-r--r--Doc/c-api/float.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/Doc/c-api/float.rst b/Doc/c-api/float.rst
index b29937d..c107243 100644
--- a/Doc/c-api/float.rst
+++ b/Doc/c-api/float.rst
@@ -22,13 +22,13 @@ Floating Point Objects
.. c:function:: int PyFloat_Check(PyObject *p)
Return true if its argument is a :c:type:`PyFloatObject` or a subtype of
- :c:type:`PyFloatObject`.
+ :c:type:`PyFloatObject`. This function always succeeds.
.. c:function:: int PyFloat_CheckExact(PyObject *p)
Return true if its argument is a :c:type:`PyFloatObject`, but not a subtype of
- :c:type:`PyFloatObject`.
+ :c:type:`PyFloatObject`. This function always succeeds.
.. c:function:: PyObject* PyFloat_FromString(PyObject *str)