TST: Test dimensions/indices found from parsed gufunc signatures. #11178
Conversation
| enabled, num_dims, ixs = umt.test_signature(2, 1, "(i1,i2),(J_1)->(_kAB)") | ||
| assert_equal(enabled, 1) | ||
| assert_equal(num_dims, (2, 1, 1)) | ||
| assert_equal(ixs, (0, 1, 2, 3)) |
There was a problem hiding this comment.
Might be nicer to build a nested tuple here, and I don't envisage it being any harder
|
I think for the testing purposes here it is perhaps better to just give back what the ufunc contains. I have been wondering more generally, though, about some way to expose this information -- maybe as simple as a nicer |
c1233ed to
d0e5e39
Compare
|
@mattip - are you happy with this going in separately? (I do apologize for hijacking your PR...) |
Arguably the ufunc just contains a representation of nested tuple, split between I don't feel strongly about this - looks like a good thing to test however you spell it |
|
LGTM, breaking the larger work into a number of smaller PRs is the way to go |
Another split-off from #11132 - expanded signature testing.