skip signature degrading

[ixje]

I just upgraded to 0.6.2 and am now facing something like this

[2020-08-27 11:14:21,239] {__init__.py:55} ERROR - Generated stubs signature is degraded to `(*args, **kwargs) -> Any` for
[2020-08-27 11:14:21,240] {__init__.py:56} ERROR - def __init__(self: neo3vm.ArrayStackItem, reference_counter: neo3vm::ReferenceCounter) -> None: pass
[2020-08-27 11:14:21,240] {__init__.py:57} ERROR -                                                                    ^-- Invalid syntax

The general idea is cool, but it would be nice if there is a cli flag to skip this downgrading. For example I do a second pass on the generates stubs to fix these myself.

[sizmailov]

Hi! The errors should motivate people to fix/report original binding code problems.

I see the extra flag as ad-hoc solution for those who generate stubs for 3rd-party libraries.

[ixje]

I see the extra flag as ad-hoc solution for those who generate stubs for 3rd-party libraries.

Fair assessment. Note that it is unclear to me if you're open to adding this flag?
I think it can be valuable if the library author isn't willing to provide stubs or is not willing to fix his bindings by way of creating forward references.

[sizmailov]

I'll merge it in a minute with a minor changes. I want to add a handy link to pybind11 doc/issue which would describe the problem with C++ signatures in docstrings.

[sizmailov]

Ok, such issue / docs paragraph does not exist (yet), can add it later.

[ixje]

@sizmailov fwiw; I think this issue describes it pybind/pybind11#2263

[sizmailov]

The "forward declaration" technique in Yannick's comment is quite useful. I use it all over the place. This example should be in pybind11 docs though.