Skip to content

Conversation

@dangotbanned
Copy link
Member

@dangotbanned dangotbanned commented Apr 1, 2025

What type of PR is this? (check all applicable)

  • 💾 Refactor
  • ✨ Feature
  • 🐛 Bug Fix
  • 🔧 Optimization
  • 📝 Documentation
  • ✅ Test
  • 🐳 Other

Related issues

Checklist

  • Code follows style guide (ruff)
  • Tests added
  • Documented the changes

If you have comments or can explain your changes, please do so below

Follow-up to this big writeup (#2294 (comment))

  • SelectorsNamespace now uses the regular Protocol class.
  • CompliantSelector is ready to change, but CompliantExpr needs switching over first

@dangotbanned dangotbanned marked this pull request as ready for review April 1, 2025 19:50
Comment on lines +112 to +115
EvalSeries: TypeAlias = Callable[
[CompliantFrameT], Sequence[CompliantSeriesOrNativeExprT]
]
EvalNames: TypeAlias = Callable[[CompliantFrameT], Sequence[str]]
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hoping to use these more now that they're not defined in selectors.py

Copy link
Member

@MarcoGorelli MarcoGorelli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks @dangotbanned !

@MarcoGorelli MarcoGorelli merged commit f932965 into main Apr 4, 2025
27 of 28 checks passed
@MarcoGorelli MarcoGorelli deleted the selectors-un-protocol38 branch April 4, 2025 09:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants