plotters VS polars

plotter-rs Cairo backend: Specific backend to interact with a gtk-rs DrawingArea widget.

I would also look at plotters https://github.com/plotters-rs/plotters to replace mathplotlib. Unfortunately, I'm not aware of any library for image transformations/augmentations.

Have you looked into plotters https://github.com/plotters-rs/plotters ? I think it should be possible to integrate it into an app.

About plots, besides plotly, take a look at https://github.com/plotters-rs/plotters and https://github.com/milliams/plotlib

I'd recommend plotters, I've only used it for it's drawing api and I found it quite nice for text rendering.

- https://github.com/plotters-rs/plotters

For those who do not know about them, polars is a data frame crate for Rust and Python. It is also the fastest data frame library, according to benchmarks. Plotters is a crate for data visualisation. Both are the equivalents of pandas and matplotlib from the Python ecosystem. However, the integration with matplotlib in pandas has no equivalent. I would like to propose an effort to integrate polars with plotters, either by modifying the existing codebases, or creating a new bridge crate. I would love to hear opinions about this from the widder community.

If you want to get into Polars, the library is very well documented, and I’d recommend you check out their getting started tutorial, their API docs, and when you’re all set up, you can also check out their Cookbooks to learn about many of the standard operations within Polars.

This is false. The polars api has used smart string for a long time.

https://github.com/pola-rs/polars/blob/32a2325b55f9bce81d019...

This is because 0.1 is in actuality the floating point value value 0.1000000000000000055511151231257827021181583404541015625, and thus 1 divided by it is ever so slightly smaller than 10. Nevertheless, fpround(1 / fpround(1 / 10)) = 10 exactly.

I found out about this recently because in Polars I defined a // b for floats to be (a / b).floor(), which does return 10 for this computation. Since Python's correctly-rounded division is rather expensive, I chose to stick to this (more context: https://github.com/pola-rs/polars/issues/14596#issuecomment-...).

https://github.com/pola-rs/polars/releases/tag/py-0.19.0

That turned out to be related to pola-rs/polars#11912, and this linked comment provided a deceptively simple solution - use PARSE_DECLTYPES when creating the connection: