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

chore: unpin NumPy to allow use of 2.0 #250

Merged
merged 1 commit into from
Sep 30, 2024
Merged

chore: unpin NumPy to allow use of 2.0 #250

merged 1 commit into from
Sep 30, 2024

Conversation

SdgJlbl
Copy link
Contributor

@SdgJlbl SdgJlbl commented Sep 30, 2024

@SdgJlbl
Copy link
Contributor Author

SdgJlbl commented Sep 30, 2024

/e2e --tests=sdk,mnist

@Owlfred
Copy link

Owlfred commented Sep 30, 2024

End to end tests: ✔️ SUCCESS

Yay! 🎉

@SdgJlbl SdgJlbl marked this pull request as ready for review September 30, 2024 10:05
@SdgJlbl SdgJlbl requested a review from a team as a code owner September 30, 2024 10:05
@ThibaultFy
Copy link
Member

The pin was to prevent incompatibilities regarding pickle. What is the issue with it ?

@SdgJlbl
Copy link
Contributor Author

SdgJlbl commented Sep 30, 2024

The pin was to prevent incompatibilities regarding pickle. What is the issue with it ?

Keeping a pin to an old version of NumPy is going to be more and more problematic down the line, as more recent versions of pandas / pytorch might not support NumPy 1.x.

If it's working with NumPy 2.x, I think we should allow it.

Do you remember when the issue with pickle was occurring?

@SdgJlbl SdgJlbl merged commit ba2eb8f into main Sep 30, 2024
8 checks passed
@SdgJlbl SdgJlbl deleted the chore/unpin-nupy branch September 30, 2024 13:24
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.

4 participants