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
Considering that this would help to expand the typehinting in that area and that the number of arguments is limited, would it be conceivable to expose all the arguments instead of relying on **kwargs?
For information this is the list of arguments that would need to be added:
Pandas version checks
main
hereLocation of the documentation
https://pandas.pydata.org/docs/reference/api/pandas.DataFrame.query.html#pandas.DataFrame.query
Documentation problem
This question arises when @MarcoGorelli wanted to fully type
DataFrame.query
in the stubs repo pandas-dev/pandas-stubs#1173. Right now the extra arguments are passed through**kwargs
but when we go through the code we see that they are the same as the ones inpd.eval
(https://pandas.pydata.org/docs/reference/api/pandas.eval.html#pandas.eval).Suggested fix for documentation
Considering that this would help to expand the typehinting in that area and that the number of arguments is limited, would it be conceivable to expose all the arguments instead of relying on
**kwargs
?For information this is the list of arguments that would need to be added:
See pandas-dev/pandas-stubs#1193 for the potential typehinting.
The text was updated successfully, but these errors were encountered: