summaryrefslogtreecommitdiffstats
path: root/Doc/c-api/complex.rst
Commit message (Collapse)AuthorAgeFilesLines
* [3.13] gh-121834: Improve `complex` C-API docs (GH-121835) (#121895)Miss Islington (bot)2024-07-171-9/+22
| | | | | | | | gh-121834: Improve `complex` C-API docs (GH-121835) (cherry picked from commit 72dccd60735b597e99c007a7b69210763a746877) Co-authored-by: sobolevn <mail@sobolevn.me> Co-authored-by: Sergey B Kirpichev <skirpichev@gmail.com> Co-authored-by: Petr Viktorin <encukou@gmail.com>
* gh-109598: make PyComplex_RealAsDouble/ImagAsDouble use __complex__ (GH-109647)Sergey B Kirpichev2024-01-151-0/+18
| | | | | | | | | | `PyComplex_RealAsDouble()`/`PyComplex_ImagAsDouble` now try to convert an object to a `complex` instance using its `__complex__()` method before falling back to the ``__float__()`` method. PyComplex_ImagAsDouble() also will not silently return 0.0 for non-complex types anymore. Instead we try to call PyFloat_AsDouble() and return 0.0 only if this call is successful.
* gh-107298: Fix more Sphinx warnings in the C API doc (#107329)Victor Stinner2023-07-271-2/+2
| | | | | | | | | | | | | | | | | | | | | | | Declare the following functions as macros, since they are actually macros. It avoids a warning on "TYPE" or "macro" argument. * PyMem_New() * PyMem_Resize() * PyModule_AddIntMacro() * PyModule_AddStringMacro() * PyObject_GC_New() * PyObject_GC_NewVar() * PyObject_New() * PyObject_NewVar() Add C standard C types to nitpick_ignore in Doc/conf.py: * int64_t * uint64_t * uintptr_t No longer ignore non existing "__int" type in nitpick_ignore. Update Doc/tools/.nitignore
* gh-106919: Use role :c:macro: for referencing the C "constants" (GH-106920)Serhiy Storchaka2023-07-211-2/+2
|
* gh-101100: Docs: Fix references to several numeric dunders (#106278)F3eQnxN3RriK2023-06-301-5/+5
| | | Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com>
* GH-97950: Use new-style index directive ('object') (#104158)Adam Turner2023-05-041-1/+1
| | | | | | | | | | | * Uncomment object removal in pairindextypes * Use new-style index directive ('object') - C API * Use new-style index directive ('object') - Library * Use new-style index directive ('object') - Reference * Use new-style index directive ('object') - Tutorial
* gh-93738: Documentation C syntax (:c:type:<C type> -> :c:expr:<C type>) (#97768)Adam Turner2022-10-051-2/+2
| | | | | :c:type:`<C type>` -> :c:expr:`<C type>` Co-authored-by: Łukasz Langa <lukasz@langa.pl>
* bpo-44426: Use of 'complex' as a C variable name confuses Sphinx; change it ↵Mark Dickinson2021-06-161-2/+2
| | | | to 'num'. (GH-26744)
* bpo-42528: Improve the docs of most Py*_Check{,Exact} API calls (GH-23602)Antonio Cuni2021-01-061-2/+2
| | | | | 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.
* bpo-20092. Use __index__ in constructors of int, float and complex. (GH-13108)Serhiy Storchaka2019-06-011-1/+7
|
* Doc: Replace the deprecated highlightlang directive by highlight. (#13377)Stéphane Wirtel2019-05-171-1/+1
| | | | highlightlang is deprecated since April 2018 in Sphinx. See https://github.com/sphinx-doc/sphinx/pull/4845
* Issue #13522: Fix _Py_co_pow() documentationVictor Stinner2011-12-181-1/+1
| | | | Patch written by Arnaud Calmettes.
* Issue #13522: document error return values of some float and complex C API ↵Antoine Pitrou2011-12-181-1/+7
| | | | functions.
* #9204: remove mentions of removed types in the types module.Georg Brandl2010-10-171-1/+1
|
* Migrate to Sphinx 1.0 C language constructs.Georg Brandl2010-10-061-33/+33
|
* Split C API docs in Py3k branch.Georg Brandl2008-01-201-0/+126
generated by cgit v0.12 at 2026-01-06 02:15:54 (GMT)