We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
One lesser known (but fully documented) feature of match.arg is it regards arg = NULL as equivalent to the first element of choices:
match.arg
arg = NULL
choices
> match.arg(arg = NULL, choices = c("stdout", "stderr")) [1] "stdout"
As a result, these two calls yield identical output:
reticulate::py_capture_output(expr, type = NULL) reticulate::py_capture_output(expr, type = "stdout")
If this is the intended behavior of py_capture_output, it might be nice to document that on the help page.
py_capture_output
If it is not the intended behavior, then perhaps py_capture_output could throw an error when type = NULL.
type = NULL
Thank you for considering.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
One lesser known (but fully documented) feature of
match.arg
is it regardsarg = NULL
as equivalent to the first element ofchoices
:As a result, these two calls yield identical output:
If this is the intended behavior of
py_capture_output
, it might be nice to document that on the help page.If it is not the intended behavior, then perhaps
py_capture_output
could throw an error whentype = NULL
.Thank you for considering.
The text was updated successfully, but these errors were encountered: