> *Although this is certainly not the case here* I believe that we will
> need to resort to this kind of ugly trick in future PRs because the
> results may be produced by a branch of statsmodel that is not merged
> yet and perhaps won't be merged, and that a fixes would be a big mess;
> of course, this should be at least documented. But we are not in this
> case here AFAIK.

But that's really a problem. Unless the data comes from a verified
source (eg the NIST statistical tables), what tells me I can trust it.

This is not a rhetoric question: in scipy people have worked in improving
the numerical stability of things like special functions. Tests like this
broke, but it was because the code was _more accurate_, not less
accurate.

We cannot just test against numbers that we don't know where they come
from and that we cannot reproduce. These are tests that will raise
problems in the long run.