[issue8952] Doc/c-api/arg.rst: fix documentation of number formats

STINNER Victor added the comment: This issue is now 5 years old and it doesn't contain much information. It's more a TODO item, and I'm not more interested to work on it. So I close the issue. If you want to work on the doc, please write a patch ;-) -- nosy: +haypo resolution: -> out

[issue8952] Doc/c-api/arg.rst: fix documentation of number formats

Changes by STINNER Victor : -- nosy: -haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue8952] Doc/c-api/arg.rst: fix documentation of number formats

Georg Brandl added the comment: It's still a valid bug. -- nosy: +georg.brandl resolution: fixed -> status: closed -> open ___ Python tracker ___

[issue8952] Doc/c-api/arg.rst: fix documentation of number formats

STINNER Victor added the comment: Three years later, nobody looks to be interested to work on this part of the documentation, so I'm closing the issue. => read the code, luke! (not the doc...) -- resolution: -> fixed status: open -> closed ___ Pyth

[issue8952] Doc/c-api/arg.rst: fix documentation of number formats

Mark Dickinson added the comment: The other variable of interest here is that some integer formats will accept types with an __index__ method, while others won't. I'm not sure which types fall into each category, right now. -- ___ Python tracker

[issue8952] Doc/c-api/arg.rst: fix documentation of number formats

Mark Dickinson added the comment: Yes, most of that paragraph is outdated. We should check exactly what does happen when the "receiving field is too small" (both in practice and in theory). In C, downcasting to an unsigned type is well-defined and will always reduce modulo 2**. The result

[issue8952] Doc/c-api/arg.rst: fix documentation of number formats

New submission from STINNER Victor : The documentation of PyArg_Parse*() number formats specify that only int / float / complex are accepted, whereas any int / float / complex compatible object is accepted. "compatible" means that it has an __int__() / __float__() / __complex__() method, or nb