Ivan Pribec

> Good point. The only reason I suggested SciPy is that I know they maintain it and fix bugs and the code should be correct and working. If we use...

The [`scipy.integrate.quad`](https://github.com/scipy/scipy/blob/4ec4ab8d6ccc1cdb34b84fdcb66fde2cc0210dbf/scipy/integrate/quadpack.py#L49) has a very similar interface to the Octave [`quad`](https://octave.sourceforge.io/octave/function/quad.html). The SciPy version is under a BSD-3 license. But I would suggest we do it jointly under the fortran-lang...

> However, I would be happy to transfer the repository to fortran-lang as it is now. I think if you follow the instructions on [transferring repositories](https://docs.github.com/en/github/administering-a-repository/managing-repository-settings/transferring-a-repository#transferring-a-repository-owned-by-your-user-account) you could transfer to...

> Is anyone involved in this thread using QUADPACK in a production code and willing to offer their code base for testing? Well there are the possibly thousands of users...

> I must say the book by Keast en Fairweather is a bit expensive (200 euros for the e-book version). The other one a bit less so. For the time-being,...

I saw I HackerNews thread about https://no-color.org/ recently. They suggest an informal standard of checking the environment variable `NO_COLOR`. Here's what the [command-line interface guidelines](https://clig.dev/#output) suggest: Disable color if your...

I was thinking instead as an optional input to `run_testsuite`. Not sure if I'd want finer grained control at the level of individual test suites, or unit tests, neither at...

One can also use an array expression like ```fortran call check(error, all(array == expected)) ```

My current plan was only to put them in the package index. 👍

Indeed, there are a few interesting ones. On my PC I found the manual for AxiSEM - a parallel spectal-element solver for 3D wave propagation (http://seis.earth.ox.ac.uk/axisem/).