Add Polars plugin

[areleu]

Overview

Hi guys, I was wondering if you are working on supporting polars: https://pola.rs/

If not I have been working on a plugin here: https://github.com/areleu/frictionless-py/tree/polars-plugin

It is still missing some tests and I have to sort out some edge cases but let me know if you are interested on including this feature. I would find it very valuable because as of the last couple of months I have been working almost exclusively with polars and not pandas.

By the way, I have been inspiring a lot from the pandas plugin so some things may look similar, my initial approach was only copying the files and working through the error messages.

[pierrecamilleri]

Hello, thank you for the proposition. As far as I know, there are no plans to implement this plugin on our side for now.

In theory, we'd be happy to integrate a plugin for polars.

In practice, if we were to integrate this plugin, would you be willing to maintain it and respond to bug reports? I'm myself not familiar with polars and the time we have to allocate to maintenance is limited after all.

[areleu]

Hello, thank you for the proposition. As far as I know, there are no plans to implement this plugin on our side for now.

In theory, we'd be happy to integrate a plugin for polars.

In practice, if we were to integrate this plugin, would you be willing to maintain it and respond to bug reports? I'm myself not familiar with polars and the time we have to allocate to maintenance is limited after all.

I would not mind helping out with bug reports and maintenance, but I may be slow depending on the time of the year. But in general I think I can respond within a week or two.

Other option is to make the plugin its own repository, is there a proper way of doing this?

[pierrecamilleri]

Other option is to make the plugin its own repository, is there a proper way of doing this?

Great question ! I am not familiar enough with frictionless to answer. @roll, what do you think ?

[roll]

I think the polars plugin is amazing!

Technically both in frictionless-py codebase, and as a separate codebase are quite the same, so I would say that the only difference is what way of maintenance is more convenient for developers.