Simon Cross

@Ericgig and I had a brief discussion about how to handle `inf` and `nan` generally. One option is forbid them entirely from the data layer -- i.e. to check and...

Idea: We could perhaps pass one extra argument called, e.g., "context" or "ctxt", that allows access to various strange things like the state. The "ctxt" object could then have properties...

I'm happy to help mitigate this in QuTiP since importing less during "import qutip" would be a good thing, but not being able to `import scipy.fftpack` when SciPy has been...

This did just bite me when trying to deploy QuTiP to MyBinder for my QuTiP SciPy tutorial and I can confirm this bug is incredibly annoying.

I was imagining something much simpler for the exception class. There is a backport of the exceptiongroup stuff to older Pythons that we could use if we wanted to: https://pypi.org/project/exceptiongroup/....

Hmm. It would be nice to get the results that succeeded. What if we made a single exception class that was used by all the functions and which contained all...

Sounds good. Perhaps we can just have `fail_fast=True` default option on all the functions.

I have found out how to use this after reading the source: ``` python -m build -n -x --wheel --config-setting="--global-option=--with-openmp" ```

One can read a little bit of somewhat useful information in PEP517 -- https://peps.python.org/pep-0517/#config-settings. I tried `--build-option` instead of `--global-option`, but that didn't work.

I've added a note to the source on this in https://github.com/qutip/qutip/pull/1978, so I'll close this issue once that is merged.