I tihnk combined with @grlee77 's changes this should work.

The problem is that sometimes tools assume that certain files outside the skimage subfolder exist.
However, we currently test with (cd .. && pytest --pyargs skimage) so most of those concerns may have already been addressed.

Most of the questions we see refer to serious installation problems that transcend what can be debugged from a python console.
Users get stuck at the import skimage step. They simply wouldn't be able to run

import skimage
simage.test()

Users interested in installing skimage on esoteric machines (High Performance Computing clusters, mobile) will generally be comfortable with the terminal and can use the pytest --pyargs skimage command. It is the same one we use to test scikit-image on the build:
https://github.com/scikit-image/scikit-image/blob/main/tools/github/script.sh#L17

This ensures we don't duplicate functionality built into pytest.

So to summarize:

If you think that asking users to run

import skimage
skimage.test()

is useful, then the code that @grlee77 is suggesting is useful.

If you think that it is just extra maintenance burden for us, then I think we should stick with pytest --pyargs skimage.

I prefer option #2. But I might be missing something critical.

Uh oh!

Bring back skimage.test #3569

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions

Bring back `skimage.test` #3569