-
Notifications
You must be signed in to change notification settings - Fork 441
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
Unpin numpy
version in its integration
#3039
base: develop
Are you sure you want to change the base?
Conversation
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Id do this instead
Co-authored-by: Hamza Tahir <[email protected]>
Describe changes
Unpining the
numpy
version.Thanks to this PR, our users will be working with
numpy>=2.0
in most cases. However, we can not define it as>=2.0
because three of our integrationsaws
(due tosagemaker)
,argilla
, andlangchain
still rely onnumpy<2.0
. This means that our testing suite will always be conducted in an environment where we havenumpy<2.0
(because we install all our integrations, which will end up downgrading the numpy version). I will manually run the tests on my end as well withnumpy>=2.0
. For those interested: Numpy 2.0 Release Notes, Numpy 2.0 Migration GuidePre-requisites
Please ensure you have done the following:
develop
and the open PR is targetingdevelop
. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.Types of changes