Hi Clément,
I'm in favour, and had a quick look at pytest-skip-slow -- it seems
essentially a simply file with definitions, and I like the idea of
having that in the astropy organization, replacing the code in
pytest-astropy.
More generally, I agree with the move to explicit test dependencies,
where specific packages just do one thing well, not *also* pull in a
whole slew of other stuff.
It is perhaps worth thinking what the purpose of pytest-astropy was, and
whether that still serves a need. I think it has evolved to become a
metapackage that allows one to set up testing for a package in the way
its done for astropy. I've certainly used it myself for that purpose,
but for my more mature packages, I've gone to more limited dependencies
that I actually use (like pytest-doctestplus and
pytest-filter-subpackage). So, for me at least, pytest-astropy pulls in
more than is needed.
On the other hand, pytest-astropy does not pull in everything astropy
testing needs, so is incomplete in that sense. To make it more useful,
one could perhaps add more dependencies to it, but, really, that use
case is more easily served by using `astropy[test]` as a test
dependendency (that assumes one's package uses astropy, but, if not,
then it would seem outside the astropy project's scope).
Overall, to me it seems pytest-astropy no longer has a compelling use
case, and (slowly) moving towards deprecating it seems sensible.
Replacing the code it has with pytest-skip-slow seems a good step also
from that perspective.
All the best,
Marten