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
With tracing I think it would be good to know where the result is coming from (firstresult=True), and/or which hook_impls have been called in general.
But this could also be useful to know in general, so storing it (optionally?) on the _Result seems like a good idea to me.
It should probably not be full references (except for when tracing is enabled, but that's not easy to know when creating the _Result it seems), but only the plugin_name by default.
With tracing I think it would be good to know where the result is coming from (
firstresult=True
), and/or which hook_impls have been called in general.But this could also be useful to know in general, so storing it (optionally?) on the
_Result
seems like a good idea to me.It should probably not be full references (except for when tracing is enabled, but that's not easy to know when creating the
_Result
it seems), but only the plugin_name by default.Related code:
pluggy/src/pluggy/callers.py
Lines 195 to 198 in a5130ac
The text was updated successfully, but these errors were encountered: