build(python): Update pyo3 and numpy crates to version 0.24

[bschoenmaeckers]

This release has significant less breaking changes than the previous one 😅

[codecov]

Codecov Report

Attention: Patch coverage is 66.66667% with 1 line in your changes missing coverage. Please review.

Project coverage is 80.90%. Comparing base (90094f0) to head (468149a).
Report is 7 commits behind head on main.

Files with missing lines	Patch %	Lines
crates/polars-python/src/conversion/datetime.rs	66.66%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #22015      +/-   ##
==========================================
- Coverage   80.99%   80.90%   -0.09%     
==========================================
  Files        1638     1639       +1     
  Lines      236856   236899      +43     
  Branches     2696     2696              
==========================================
- Hits       191840   191671     -169     
- Misses      44382    44594     +212     
  Partials      634      634              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[bschoenmaeckers]

I'm currently unable to fix the clippy error. It reports a unused import but when expanding the impl_set_with_mask or converting it into a concrete implementation, the error goes away.

[ritchie46]

I'm currently unable to fix the clippy error. It reports a unused import but when expanding the impl_set_with_mask or converting it into a concrete implementation, the error goes away.

Can we than silence that lint for that specific code snippet?

[bschoenmaeckers]

I'm currently unable to fix the clippy error. It reports a unused import but when expanding the impl_set_with_mask or converting it into a concrete implementation, the error goes away.

Can we than silence that lint for that specific code snippet?

I spammed #[allow(unused_imports)] all over the macro but I could not fix this locally. But luckily the issue is fixed upstream and will be released in pyo3 0.24.2.