polars-ocaml icon indicating copy to clipboard operation
polars-ocaml copied to clipboard

Results 30 polars-ocaml issues
Sort by recently updated
recently updated
newest added

https://github.com/akabe/ocaml-jupyter seems pretty straightforward to integrate into polars-ocaml; we should probably add some functionality so that the dataframes / series are rendered in a prettier way in jupyter but doesn't...

An attempt to port over changes in https://github.com/TheNumbat/polars-ocaml

This makes it easier to use opam 2.2 and makes cold starts faster since you can use opam 2.2 and the base switch included in the base image.

When trying to build the project in a dev container, we seem to get the following linking-related error: ``` # dune build @fmt @runtest @doc File "lib/dune", line 41, characters...

Currently, we're on [version 0.32.1 of the polars library](https://github.com/mt-caret/polars-ocaml/blob/dcd5cd9cf8575cb2a5012329f694570ea92a247e/rust/polars-ocaml/Cargo.toml#L23), but the latest version is [0.34.2](https://docs.rs/polars/0.34.2/polars/index.html). We should bump the version and fix anything that breaks.

[Database IO support](https://github.com/pola-rs/polars/blob/63e1dbf5a09feaf8e673ba8f87b05ddf499632c0/py-polars/polars/io/database.py) (along with AWS and Bigquery support as well) mostly just uses Arrow + `pl.from_arrow`; a good OCaml Arrow transport story is most likely a blocker for this.

I think it's possible to write an `ToOCaml` instance for iterators, which would let us do this.

The only sources of SEGV issues so far were: - polars bugs - mis-specifying types on the OCaml side in `extern`s The second case is a bit scary, and I...

ci