Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: have skewness match pyspark #307

Merged
merged 1 commit into from
Feb 16, 2025

Conversation

eakmanrq
Copy link
Owner

Resolves: #306

@eakmanrq eakmanrq force-pushed the eakmanrq/have_skewness_match_pyspark branch from a99411d to 890da21 Compare February 16, 2025 17:38
@eakmanrq eakmanrq merged commit 1d99abb into main Feb 16, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

bug: F.skewness returns different results for pyspark and duckdb sessions (sample vs population skewness)
1 participant