diff options
| author | Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> | 2021-01-06 12:54:18 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-01-06 12:54:18 (GMT) |
| commit | faf49573963921033c608b4d2f398309d9f0d2b5 (patch) | |
| tree | 92cc19ba1878beb393127731cb1b499fa35feca1 /Lib/enum.py | |
| parent | a3ca6747f50efa2fe59caf516a26b0fd1912b8e8 (diff) | |
| download | cpython-faf49573963921033c608b4d2f398309d9f0d2b5.zip cpython-faf49573963921033c608b4d2f398309d9f0d2b5.tar.gz cpython-faf49573963921033c608b4d2f398309d9f0d2b5.tar.bz2 | |
bpo-42528: Improve the docs of most Py*_Check{,Exact} API calls (GH-23602) (GH-24139)
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.
(cherry picked from commit 315fc52db17b19fe30aa9193f26adf69e18d8844)
Co-authored-by: Antonio Cuni <anto.cuni@gmail.com>
Co-authored-by: Antonio Cuni <anto.cuni@gmail.com>
Diffstat (limited to 'Lib/enum.py')
0 files changed, 0 insertions, 0 deletions