Description

eriknw

opened on May 21, 2022

Issue body actions

I see no reason why these shouldn't exist in indexunary namespace. Any reason for their omission @jim22k?

Also, I noticed that select and indexunary are both directories with a single __init__.py. Unless we expect to put more files in these (such as numpy.py), I would change these to select.py and indexunary.py.

Activity

1. eriknw

   added

   enhancementImprove existing functionality or make things work betterImprove existing functionality or make things work better

   featureSomething is missingSomething is missing

   on May 21, 2022
2. jim22k commented on May 21, 2022

   

   jim22k

   on May 21, 2022

   Member

   More actions

   Just an assumption that they wouldn't be used much if at all in indexunary, so I didn't include them. I'm not opposed to someone adding them.
3. eriknw commented on May 21, 2022

   

   eriknw

   on May 21, 2022

   MemberAuthor

   More actions

   Gotcha. I was playing around with mask recipes (shocking, I know), and one recipe for m1 as value mask (such as A.V) and m2 as any other mask is:

   val = indexunary.valuene(m1.parent, False).new(dtype, mask=m2)
   val(val.V, replace=True) << True  # or select.nonzero

   And I was surprised that the indexunary.value helper wasn't there.
4. eriknw

   added

   good first issueClearly described and easy to accomplish. Good for beginners to the project.Clearly described and easy to accomplish. Good for beginners to the project.

   good second issueClearly described, educational, but less trivial than "good first issue".Clearly described, educational, but less trivial than "good first issue".

   on May 21, 2022
5. eriknw

   added a commit that references this issue on Aug 5, 2026

   Add indexunary.value/row/column helpers accepting comparison expressi…

   3379d9d

Issue actions