Zverev Konstantin

There is [parse_generics_shim](https://docs.rs/parse-generics-shim/*/parse_generics_shim/index.html), which is macro from closed RFC, that allows parsing generics and where clause in macro, it's limited, but possible solution.

Is there any blockers on this? I really [wish](https://github.com/rust-lang/rfcs/issues/2262) there is some `Read`/`Write` traits accepted by the ecosystem (especially async). Otherwise most of the `no_std` bail out to `core::fmt::Write`, which...

Facing similar issue, but only with some workers (1-2 out of 9 and growing). Profiled them with cProfile. Here is "normal" worker profile.  And here is profile of workers...

It's hard to measure exactly, because of variety of possible use cases. But speedup is small, which is anticipated. In my production use case constructing pl.Expr and pl.LazyFrame with all...

Ready to be merged or closed :neutral_face:

@alexander-beedie Sorry for disappearance. Rebased main.

@deanm0000 `pl.Expr.some_func = ...` modifies class `__dict__`, which is still in place. But this would prevent ``` instance = pl.col("a") instance.some_func = ... ``` Also suggesting to take a look...

It would also be great if scan_* and read_* functions had unified input "type" for files\bytes\etc.. Also it will be nice so that they accepted list of BytesIO or path-like,...

Difference between lazy/eager seems to be fixed on main. Now both eager and lazy have 0 sums. Lazy ``` shape: (9, 3) ┌──────────┬──────────┬─────────┐ │ Column_A ┆ Column_B ┆ New Sum...

Well, then registration of namespace would be better handled by using [descriptors](https://docs.python.org/3/howto/descriptor.html). Like this. Will experiment on this once I get to PR. ```python class Namespace: def __get__(self, obj, objtype=None):...