Nice. As for pytest, it seems the .pytest directory is being created by pytest cache. There is a note that it can be disabled like any plugin, something like python -m pytest -p no:cacheprovider. I wonder if we can add that to np.test() by default

This will still create a .hypothesis directory when run from a git checkout via python runtests.py ..., correct? So we still need to add .hypothesis to .gitignore

This will still create a .hypothesis directory when run from a git checkout via python runtests.py ..., correct? So we still need to add .hypothesis to .gitignore

If python runtests.py ... avoids importing or executing numpy.conftest, yes it will... and we'd miss all the other Hypothesis config too in that case.

Otherwise, we should have the same setup as the other ways to run tests which redirects everything to tempfile.gettempdir() + "/.hypothesis regardless of working directory. No harm in adding .hypothesis/ to gitignore though, and I can imagine odd scenarios where it would be useful.

On the one hand, with this PR I no longer have a .hypothesis directory in ./build/testenv/lib/python3.7/site-packages/.hypothesis. However, I see a warning with pytest=5.4.3

/home/matti/miniconda3/envs/numpy/lib/python3.7/site-packages/_pytest/config/__init__.py:935
  /home/matti/miniconda3/envs/numpy/lib/python3.7/site-packages/_pytest/config/__init__.py:935: PytestAssertRewriteWarning: Module already imported so cannot be rewritten: hypothesis
    self._mark_plugins_for_rewrite(hook)

-- Docs: https://docs.pytest.org/en/latest/warnings.html

@mattip - I've moved the import hypothesis to after import pytest in the __call__ method, which I'm pretty sure will fix that warning.

Thanks @Zac-HD

I've moved the import hypothesis to after import pytest in the __call__ method

@Zac-HD The warning still appears

Maybe hypothesis is being imported somehow before the __call__ method is called? I don't know what's happening through, sorry.