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
Right now inspect.getargvalues treats p, a, and b the same way. It is not very useful. How caller can do anything with these arguments if they all have different semantics? p must always be possitional, a can be both, b can only be keyword argument.
I propose adding inspect.signature support for frame objects and use it.
For example, adding to Signature class
@classmethoddeffrom_frame(cls, frame): ...
will provide a new API to do the same thing, but correctly.
The text was updated successfully, but these errors were encountered:
Here's an example:
Right now
inspect.getargvalues
treatsp
,a
, andb
the same way. It is not very useful. How caller can do anything with these arguments if they all have different semantics?p
must always be possitional,a
can be both,b
can only be keyword argument.I propose adding
inspect.signature
support forframe
objects and use it.For example, adding to
Signature
classwill provide a new API to do the same thing, but correctly.
The text was updated successfully, but these errors were encountered: