Skip to content

Conversation

@dangotbanned
Copy link
Member

Closes #2500

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

(#2733) reminded me that this was long overdue πŸ˜…

Surfaced some gaps we had hiding behind the Any

@dangotbanned dangotbanned added internal typing pyspark Issue is related to pyspark backend duckdb Issue is related to duckdb backend dask Issue is related to dask backend pyspark-connect polars Issue is related to polars backend labels Jun 28, 2025
@dangotbanned dangotbanned marked this pull request as ready for review June 28, 2025 19:39
@dangotbanned

This comment was marked as resolved.

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 , really nice!

@MarcoGorelli MarcoGorelli merged commit eb81991 into main Jun 28, 2025
37 of 38 checks passed
@MarcoGorelli MarcoGorelli deleted the proto-expr-namespace-2 branch June 28, 2025 20:41
dangotbanned added a commit that referenced this pull request Jul 31, 2025
- Left over from #2756
- Need to merge #2897 first and rebase
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dask Issue is related to dask backend duckdb Issue is related to duckdb backend internal polars Issue is related to polars backend pyspark Issue is related to pyspark backend pyspark-connect typing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add protocols for LazyExpr*Namespace

3 participants