It looks like we have problems building on PyPy3.10 because NumPy doesn't have wheels yet numpy/numpy#26141

Also, not sure if the original test condition on the ipynb test is wrong, since it's failing here.

I think we just skip pypy310 on at least windows, maybe all platforms.

I added a ipykernel==5.5.6 requirement to the older ipython job, as pip was walking back the versions to find a compatible one, so probably best to help it along with a pin.

However, test_ipynb is failing, and it seems like we are getting module://ipykernel.pylab.backend_inline instead of our expected module://ipykernel.pylab.backend_inline, and I'm not sure why it's only happening now with Python 3.10 instead of the older 3.9, but I can reproduce locally. cc @ianthomas23

I think your ipython pin should be 7.29.0 as that was released in October 2021, the same month as Python 3.10. That is consistent with ipykernel 5.5.6. The test passes locally for me using these.

I forgot about Cygwin here; I believe they only have 3.9, and the plan is to jump to 3.12 directly: numpy/numpy#26222 (comment)

We'll have to disable it in the meantime.

Could we also add a minimum pin for python in environment.yml? For some reason mamba gives me 3.9 by default, but it also resolves fine if I pin it higher.