matt

> In this version, if I need to tranport `PyLazyFrame` between Python and Rust, what python polars version should I use? I tried with version `1.29.0`, but faled. Ah, that...

> Suppose I have this pyo3 function: > ... > > The same logic should work for `PyLazyFrame` too. This (and the weird non-rust error with `/example/extend_polars_python_dispatch` is happening in...

I came here to make the same suggestion in fact. I'm guessing this feature does not yet exist, and if that is the case would you mind if I took...

Thanks for the interest! Yes, that approach could definitely work. However, it also feels like it could be a bit of a hack in the sense that it keeps the...

@nikolassv would you be open to considering the use of JSON for the log file? This could be done in a 100% backward-compatible manner, and would also make future additions/changes...

While I cannot say I 100% agree with the thinking, I do very much see your point and also appreciate you clearing up how you envision the hashtags approach working....

Apologies for dropping off for so long, work and all. I have picked this up again and run into a problem of the "how should this work?" variety. Assume a...

Thanks, that works and I should be able to put it together quickly! Although likely not as soon as I would want.

@bluss I noticed this PR the other day and thought it might be worth mentioning that a very similar thing was done in a recent student project [here](https://github.com/csiro-energy-systems/circuit-graphs/blob/main/src/lib.rs#L401C1-L460C10). Your approach...

May I suggest that the documentation contain a note/warning added about the size of the result being potentially quite large in the case where the graph contains parallel edges?