Skip to content

Conversation

@lemorage
Copy link
Contributor

As said in #616, this PR adds support for numpy type binding at the scalar number level.

Will close #616.

@lemorage
Copy link
Contributor Author

Thanks for the detailed explanations, I misunderstood a bit from the suggested proposal. I am looking into those issues.

@lemorage lemorage force-pushed the handle-numpy-vector branch from 2c135fc to 448e3a3 Compare June 16, 2025 15:47
@lemorage
Copy link
Contributor Author

lemorage commented Jun 16, 2025

@badmonster0 Do u have any idea why the formatting check is always failing, even though it works well locally?

(cocoindex) ☁  cocoindex [handle-numpy-vector]  ruff format python/cocoindex/tests/test_typing.py
1 file left unchanged
(cocoindex) ☁  cocoindex [handle-numpy-vector]  ruff --version
ruff 0.6.8

@lemorage lemorage force-pushed the handle-numpy-vector branch from 448e3a3 to 2f4ac25 Compare June 17, 2025 05:55
@lemorage
Copy link
Contributor Author

Turns out it is due to version diffs.

@lemorage lemorage force-pushed the handle-numpy-vector branch from 1b02448 to 48bbbaf Compare June 17, 2025 12:59
@badmonster0 badmonster0 merged commit 316cdf3 into cocoindex-io:main Jun 18, 2025
5 checks passed
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.

[FEATURE] Support Int64/Float32/Float64 to be bound with corresponding numpy number types

2 participants