Pablo Winant

I have now removed all parts from the source which involve `std:jstream`. Now compilation fails during the linking step with `error: "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)."`

Hmm, that is very clear. Now the situation starts to get more complicated as I need to find a way to have meson build a python extension_module without the python...

Sounds perfect. This conda world never ceases to amaze me! Do you have any example of a package that uses it by any chance?

It feels so close ! I added a test but the error message I get from CI seems (superficially) unrelated to it.

I didn´t add it explicitly. I've tried locally to add `-s SIDE_MODULE=1` to the linker but had no effect. However putting `-s SIDE_MODULE=0` results in another error during the test...

Ok, I've added `-s SIDE_MODULE=1` to the compiler options, but I suppose it was already the default with meson python extension.

Ok, now I don't know. The error on CI: ```RuntimeError: [Error('LinkError: WebAssembly.instantiate(): Import #404 module="env" function="memory": mismatch in shared state of memory, declared = 1, imported = 0'), TimeoutError('Timeout 240000ms...

@DerThorsten : do you have any idea of where to go next on this ?

Derivatives are now available in interpolation.py (doc here https://www.econforge.org/interpolation.py/splines/)

Derivatives are now available in interpolation.py (doc here https://www.econforge.org/interpolation.py/splines/)