Closed Michael-J-Ward closed 1 month ago
@haixuanTao the last deprecation warning was here.
I think that the new bounds API makes this unnecessary, and the deprecation warning states "code not using the GIL Refs
API can safely remove the use of Py::new_pool
".
I included that change as the last commit, so if you find that it is still necessary it'll be an easy rollback.
@haixuanTao the last deprecation warning was here.
I think that the new bounds API makes this unnecessary, and the deprecation warning states "code not using the
GIL Refs
API can safely remove the use ofPy::new_pool
".I included that change as the last commit, so if you find that it is still necessary it'll be an easy rollback.
That makes sense, thanks!
This fix an issue that I had about stopping a dataflow that has been present for a bit!
Thanks a lot!
Can't wait to merge it.
@haixuanTao - It could be a few months before arrow-rs
gets released.
If you don't mind pointing to arrow-rs
's master, then I'll rebase this so you can merge now, and I'll update the deps once it does get released.
If we merge it, we will not be able to publish on cargo, which will makes our release stuck. So I wouldn´t do it.
What we could do, is to only merge arrow version within dora-node-api-python that is distributed using pip which does not check for git packages and distribute dora-node-api-python with the latest arrow.
But not sure if we can handle multi arrow versions.
@haixuanTao This is rebased and ready for review.
pyo3 0.21 is in
arrow-rs
master (see https://github.com/apache/arrow-rs/pull/5566), but not yet released.Notes
After updating the deps, this was completely a compiler / clippy driven refactor where clippy highlights deprecation warnings, and I would update using the migration guide.
I did not go looking for any other opportunities to use the new
Bounds
api.