Consider supporting polars about exchange_calendars HOT 6 OPEN

👍 That definitely seems like the way to go for performance and flexibility. Rust is still stuck on my todo list ☹️

I'm wondering to what degree it would complicate the build and installation?

from exchange_calendars.

I'm wondering to what degree it would complicate the build and installation?

pyo3/maturin (https://www.maturin.rs/) are pretty well supported these days. We'd basically build wheels for everything and most users would just install the wheel (https://github.com/pydantic/pydantic-core/blob/main/.github/workflows/ci.yml#L446). So the build side for us would be more involved but mostly the same for the vast majority of users. Some users will build from source, but I think that's relatively uncommon/plenty of other libraries are bundling rust already.

I think figuring out the right parts of the api to support rust + pandas + polars would be a bit annoying but doable.

from exchange_calendars.

Sounds good. I've certainly noticed Rust pushing it's way into python projects.

Learning Rust is on my 2024 todo list. Unfortunately I can't see that I'll be in a position to offer any help until, at best, towards the end of the year...

from exchange_calendars.

No problem! I was going to see if I could carve out a weekend or some time on a flight to try to make a branch.

from exchange_calendars.

One thing that doesn't seem to sit right with this library is that it's on a fork. I was wondering whether any move to Rust and support for polars would justify starting over with a fresh library and just crediting the quantopian roots?

Just a thought.

from exchange_calendars.

I've definitely been annoyed by that.

I agree that maybe it would be good to develop in a new repo and then archive this one when we're ready (and do a major version update).

from exchange_calendars.