Albert Steppi

Thanks @bgyori. I can fix these over the weekend.

I see. The reason it’s on 1.11.2 instead of 1.12 is because the docs were built before Pyodide released 0.26, and to enable the interactive examples we just unhid the...

I think just adding a sentence stating that the SciPy version running in the browser may be older than the one being documented would be helpful and sufficient.

> doc build artifacts that encode that version or generated content that depends on it, beyond a single `scipy` or `scipy==1.x.y` (or even `pyodide-kernel` or some such thing) dependency specifier...

> In there are no objections, I'd like to hit the button with this one. I'll give it a quick review and hit the button today.

> Is there a good way to test only this one file, in light of `python dev.py test -v` failing? We should try to get your local dev environment working...

@JasonGross, did you build SciPy with `python dev.py build` successfully and it's only `python dev.py test -v` that fails? Did you follow all the steps [here](https://docs.scipy.org/doc/scipy/building/index.html) for building from source...

What's the output of `echo | gcc -v -E -`? Among other things, this will show which paths gcc searches for header files.

I see, your gcc will search ``` /usr/include /home/jgross/.local64/mambaforge/envs/scipy-dev/include/python3.11 /home/jgross/.local64/mambaforge/envs/scipy-dev/include /home/jgross/.local64/mambaforge/envs/scipy-dev/bin/../lib/gcc/x86_64-conda-linux-gnu/12.3.0/include /home/jgross/.local64/mambaforge/envs/scipy-dev/bin/../lib/gcc/x86_64-conda-linux-gnu/12.3.0/include-fixed /home/jgross/.local64/mambaforge/envs/scipy-dev/bin/../lib/gcc/x86_64-conda-linux-gnu/12.3.0/../../../../x86_64-conda-linux-gnu/include /home/jgross/.local64/mambaforge/envs/scipy-dev/bin/../x86_64-conda-linux-gnu/sysroot/usr/include ``` `/usr/include/x86_64-linux-gnu` isn't there, that's why the `timesize.h` on your machine isn't found. I don't use...

> Ah, sorry, I guess I was premature with the CI before. > > Btw, you might want to update the build instructions, I had to do > > ```...