refactor(python): Split file of lazyframe methods

[eitsupi]

As with DataFrame, it would be better to split the io-related functions into separate files for LazyFrame as well.

[codecov]

Codecov Report

Attention: Patch coverage is 99.34354% with 3 lines in your changes missing coverage. Please review.

Project coverage is 79.48%. Comparing base (414d883) to head (0bca62c).
Report is 120 commits behind head on main.

Files with missing lines	Patch %	Lines
crates/polars-python/src/lazyframe/io.rs	99.34%	3 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##             main   #19937       +/-   ##
===========================================
+ Coverage   59.28%   79.48%   +20.19%     
===========================================
  Files        1555     1556        +1     
  Lines      216180   216181        +1     
  Branches     2456     2456               
===========================================
+ Hits       128155   171824    +43669     
+ Misses      87467    43799    -43668     
  Partials      558      558               

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

[ritchie46]

This on itself is fine, though we are not going to merge this because we want to revert all the splits. It is a requirement needed to get Polars working in WASM. See more context: PyO3/pyo3#2517

[eitsupi]

This on itself is fine, though we are not going to merge this because we want to revert all the splits. It is a requirement needed to get Polars working in WASM. See more context: PyO3/pyo3#2517

@ritchie46 Thanks for the reply, but do that restriction really still exist today?
I know @georgestagg was working on builds for polars for pyodide, and from looking at its source code it seems to have been successfully built with multiple pymethods intact.
https://github.com/georgestagg/polars/releases

[georgestagg]

Indeed. My method works but requires using a custom LLVM & Rust compiler to support multiple pymethods with Wasm.

I'm working on upstreaming the changes required to LLVM here.

EDIT: The above PR is merged, but more work is still required. Another PR to LLVM will be needed, and then we must wait for the changes to hit rustc, amongst some other work. It may be that refactoring Polars to avoid multiple pymethods is faster, but I don't know for sure how much work that involves.

[eitsupi]

@georgestagg Thanks, amazing!

@ritchie46 Given that removing multiple pymethods would make the code significantly less readable, might it be better to keep the file split in favor of llvm/llvm-project#111008?

[eitsupi]

@ritchie46 Could you reopen this?

[ritchie46]

@georgestagg that's awesome. Could I contact you/ have a quick call? I'd like to learn more about this.

[georgestagg]

@ritchie46 Sure, feel free to contact me at georgestagg [at] gmail [dot] com