New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
not compatible with pydantic.validate_arguments #402
Comments
|
Thanks for raising this. I'm marking it as a bug. It looks like the call to foo is failing at Lines 475 to 480 in 37c4305
This is surprising, because calling foo without arguments normally (i.e. without _CallAndUpdateTrace) passes pydantic's validation, but making the call with _CallAndUpdateTrace fails validation. Looking deeper, I see the arguments being used to call foo by _CallAndUpdateTrace are different than when calling foo directly. This is determined by these lines: Lines 682 to 683 in 37c4305
When this is run, varargs takes on the value |
|
See also #343 -- in that issue @melsabagh-kw shows a decorator he wrote to get typeguard typechecking with fire. |
|
Can I look into this? @dbieber |
|
Yes, just please be advised that we don't have any planned review time for accepting PRs right now, so it might be a while before we can provide feedback or accept your proposed change. |
A function with
Fieldparameter wrapped bypydantic.validate_arguments, can not been exeuted from the command line.run this code from command line with raise:
The text was updated successfully, but these errors were encountered: