Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Use Numpy 2.0 for Python 3.9+ packages#1002

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
asmorkalov merged 1 commit intoopencv:4.xfromasmorkalov:as/numpy_2.0_v2
Jun 17, 2024

Conversation

asmorkalov
Copy link
Collaborator

@asmorkalovasmorkalov commentedJun 17, 2024
edited
Loading

Numpy 2.0 is backward compatible with 1.x, but introduce several API and ABI changes. Numpy authors claim, that packages built against Numpy 2.0 should work with 1.x too. The PR introduce additional packages built with Python 3.9 and Numpy 2.0.

Numpy release details:https://github.com/numpy/numpy/releases/tag/v2.0.0

The PR differs from#1001. It builds packages with limited API cp37, but with Python 3.9 and Numpy 2.0. It's expected that the package should work with all supported Pythons 3.7+ and Numpy 1.x and 2.x.

@asmorkalovasmorkalov changed the titleWIP: Alternative solution to use Numpy 2.0 for Python 3.9+ packagesUse Numpy 2.0 for Python 3.9+ packagesJun 17, 2024
@@ -4,13 +4,9 @@ requires = [
"numpy==1.13.3; python_version=='3.6' and platform_machine != 'aarch64' and platform_machine != 'arm64'",
"numpy==1.17.0; python_version=='3.7' and platform_machine != 'aarch64' and platform_machine != 'arm64'",
"numpy==1.17.5; python_version=='3.8' and platform_machine != 'aarch64' and platform_machine != 'arm64'",
"numpy==1.19.3; python_version<='3.9' and sys_platform == 'linux' and platform_machine == 'aarch64'",

Choose a reason for hiding this comment

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

We need explicit<2 insetup.py for Python 3.8 and earlier in case of possible expanding of numpy2 releases.

Choose a reason for hiding this comment

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

It would clarify the actual state, but the current version works as well since numpy itself haspython_requires>=3.9, so numpy 2.0 and later cannot be installed with older Python versions.

The added constraints here look good to me.

sergregory, opencv-alalek, and Wh1isper reacted with thumbs up emoji
Copy link
Collaborator

@sergregorysergregory left a comment

Choose a reason for hiding this comment

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

LGTM

@caldempsey
Copy link

🙏

@asmorkalovasmorkalov merged commitcce7c99 intoopencv:4.xJun 17, 2024
185 of 189 checks passed
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@rgommersrgommersrgommers left review comments

@opencv-alalekopencv-alalekopencv-alalek left review comments

@sergregorysergregorysergregory approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

5 participants
@asmorkalov@caldempsey@rgommers@sergregory@opencv-alalek

[8]ページ先頭

©2009-2025 Movatter.jp