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
It seems like if I use a kwargs, pluggy will ignore this argument and won't call it anymore. I can see that HookImpl stores both kwargsnames and argnames but only argnames are called. Is this intentional or bug? I try to search in the docs but couldn't find anything related.
naming markers: HookSpecMarker and HookImplMarker must be initialized with the name of the host project (the name parameter in setup()) - so eggsample in our case.
But it never mentioned keywords arguments cannot be used.
p.s. I did a bit more digging, it seems that kwargnames is never used anywhere in the source code other than saving it as an attribute.
The text was updated successfully, but these errors were encountered:
@RonnyPfannschmidt Where can I find the related discussion? If it's not going to be implemented soon, does it makes sense to document this behavior for the time being? It would be great to get a view from pluggy standpoint as our users thought this is a bug on our side. We can add a few sentences in our own docs, but it will be nicer to reference pluggy's doc directly.
Something like `keyword arguments is not supported yet" is good enough.
Description
I try to set default argument for a hook and find it does not work.
It seems like if I use a
kwargs
,pluggy
will ignore this argument and won't call it anymore. I can see thatHookImpl
stores bothkwargsnames
andargnames
but onlyargnames
are called. Is this intentional or bug? I try to search in the docs but couldn't find anything related.Context
pluggy/src/pluggy/_callers.py
Lines 71 to 73 in 5c16e15
In docs, it said:
But it never mentioned keywords arguments cannot be used.
p.s. I did a bit more digging, it seems that
kwargnames
is never used anywhere in the source code other than saving it as an attribute.The text was updated successfully, but these errors were encountered: