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.

Sign up for GitHub

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

Jump to bottom

Numpy 2.0+ support #3205

Open
jvesely opened this issue Feb 20, 2025 · 0 comments
Open

Numpy 2.0+ support #3205

jvesely opened this issue Feb 20, 2025 · 0 comments
Assignees
@jvesely
Labels
deps Dependency update fixed-in-devel The issue is fixed in 'devel' branch and will be included in the next release

Comments

@jvesely
Copy link
Collaborator

jvesely commented Feb 20, 2025 •
edited
Loading

This issue tracks adaptations to new behavior in Numpy 2.0
see https://numpy.org/devdocs/numpy_2_0_migration_guide.html.

Moreover, fastkde <2.1 fails with Numpy 2. and fastkde 2.1+ doesn't work with Numpy 1.x (LBL-EESA/fastkde#53), so they need to be updated in sync
@jvesely jvesely self-assigned this Feb 25, 2025
@jvesely jvesely added the deps Dependency update label Feb 26, 2025
@jvesely jvesely mentioned this issue Feb 26, 2025
Merged
jvesely added a commit that referenced this issue Mar 11, 2025
@jvesely
deps: Fix issues and enable Numpy 2+ (#3219)
51f6292 
Don't call np.all on a generator.
Use greedy regexp match to remove function/construction call arguments.
Use convert_to_np_array helper in AutodiffComposition.
Explicitly check for empty arrays when converting ContentAddressableMemory weights to integers.

Allow the latest numpy and fastkde packages.

Closes: #3205
@jvesely jvesely added the fixed-in-devel The issue is fixed in 'devel' branch and will be included in the next release label Mar 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jvesely jvesely

Labels
deps Dependency update fixed-in-devel The issue is fixed in 'devel' branch and will be included in the next release
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jvesely