You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The documentation needs some more detail on these areas because:
It doesn't mention why Arguments.type_comment_args and FunctionDef.type_comment_args both exist. Perferably some examples would be included.
It specifies the types of many of these fields as NodeNG, when they're probably only Subscript, Const, or Name nodes.
It doesn't mention that Arguments.type_comment_args is prepended with a None when the first argument is a (correctly) non-annotated self or cls argument.
Using these fields to get type information is incredibly difficult. It requires doing a complex merge operation of the various type fields to figure out what's actually being used. We could provide either a utility to do this, or some example code. Example code may help to explain what each field is for.
The text was updated successfully, but these errors were encountered:
The documentation needs some more detail on these areas because:
Arguments.type_comment_args
andFunctionDef.type_comment_args
both exist. Perferably some examples would be included.Subscript
,Const
, orName
nodes.Arguments.type_comment_args
is prepended with aNone
when the first argument is a (correctly) non-annotatedself
orcls
argument.The text was updated successfully, but these errors were encountered: