Antoine Pitrou
Antoine Pitrou
That was just a random suggestion, no need to act on it here.
AFAIK, printing with enough precision is implemented by a bunch of open source libraries, including Google's own [double-precision](https://github.com/google/double-conversion).
I like option 2 better. I suppose we'd have to take the GIL and call the CPython warnings API.
Well as long as we support only a couple signatures (e.g. `np.sum(a)` and `np.sum(a, axis=...)`), then it shouldn't be a problem. It's when there's some combinatorial explosion in argument signatures...
@lucasjinreal Please stop this.
No, it seems to apply to all methods of `cdef` classes, though the symptoms are slightly different (`__init__` and `__new__` have a generic signature, other methods have no signature at...
Note the goal for `__text_signature__` is to interpretable by `inspect.signature`. I hope Sphinx's autodoc will handle that.
By the way, it seems `__text_signature__` is normally generated, on C functions, from the first line of the docstring: https://github.com/python/cpython/blob/master/Modules/clinic/_bisectmodule.c.h#L6
Are there any downsides to enabling the `binding` directive? The documentation doesn't seem to say anything.
Well, I may be missing something, but I have the following Cython code (excerpt): ```cython # cython: language_level = 3 # cython: binding = True cdef class ModeOptions(FunctionOptions): __doc__ =...