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
Currently select bends over backwards trying to make specifying with siu expressions, also work when just plain lambdas are used.
For example
select(_.a, _.b) select(lambda _: _.a, lambda _: _.b)
select(lambda _: _.contains("a"))
The last statement works because the lambda will be passed a VarSelect instance. However, this has two limitations:
_["a": "b"]
slice
If we change select to...
Then it opens room for people to use their own functions with select, and provides an easy to understand behavior in this case.
The text was updated successfully, but these errors were encountered:
See #365
Sorry, something went wrong.
Let's remove the use of a pandas Series while we're at it. This will let us remove pandas imports from the sql verb module.
No branches or pull requests
Currently select bends over backwards trying to make specifying with siu expressions, also work when just plain lambdas are used.
For example
The last statement works because the lambda will be passed a VarSelect instance. However, this has two limitations:
_["a": "b"]
with the object it creates downstream, aslice
.If we change select to...
Then it opens room for people to use their own functions with select, and provides an easy to understand behavior in this case.
The text was updated successfully, but these errors were encountered: