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

Switch from pyzstd to zstandard #1514

Merged
merged 1 commit into from
Apr 2, 2024
Merged

Switch from pyzstd to zstandard #1514

merged 1 commit into from
Apr 2, 2024

Conversation

josnyder-2
Copy link
Contributor

The zstandard library has clearer maintainership. I have also taken this opportunity to sort the list of requirements.

Copy link
Collaborator

@etr2460 etr2460 left a comment

Choose a reason for hiding this comment

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

lgtm! i didn't see any usage of zstd_open in the repo, so the only people this may impact is those writing their own evals and running them. I'll add this to patch notes when we do the next release (and possibly version bump since this might be a breaking change (returning a different type in this function))

@etr2460 etr2460 merged commit b5853eb into main Apr 2, 2024
1 check passed
@etr2460 etr2460 mentioned this pull request Apr 17, 2024
etr2460 added a commit that referenced this pull request Apr 17, 2024
Release 3.0.0 of evals. This is a major version bump because
#1514 was a breaking change to how
we handle zstd files
varad-newtuple pushed a commit to varad-newtuple/openai_eval that referenced this pull request Oct 4, 2024
Release 3.0.0 of evals. This is a major version bump because
openai/evals#1514 was a breaking change to how
we handle zstd files
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.

2 participants