Flexible and powerful data analysis / manipulation library for Python, providing labeled data structures similar to R data.frame objects, statistical functions, and much more
For code-sharing purposes we re-use ops.arith_method_FRAME for both flex and non-flex methods. As a result, the non-flex methods have the flex signature, and accept arguments not generally accepted by dunder methods. We even have a few tests e.g.
result = d.__and__(s, axis="columns")
result = d.__and__(s, axis=0)
in tests.frame.test_operators.
Should we disallow passing these arguments? Is it relevant that we do not have flex versions of and/or/xor?
For code-sharing purposes we re-use ops.arith_method_FRAME for both flex and non-flex methods. As a result, the non-flex methods have the flex signature, and accept arguments not generally accepted by dunder methods. We even have a few tests e.g.
in tests.frame.test_operators.
Should we disallow passing these arguments? Is it relevant that we do not have flex versions of and/or/xor?