Repository navigation
Move test runner out of astropy core #6362
Description
Activity
Yes, this issue has already been discussed elsewhere. I thought about it from time to time... We had a GSoC proposal to implement each option as a separate pytest plugin, which I think is a good idea but need some dedicated resources to make it happen.
Oops, I was just searching for the wrong terms. I'll take a look and see if this is something I can help with.
@pllim - The hard limit for this is 3.0, as we've already removed the deprecated compatibility code from the helpers, but tagged it for 3.0 to not put extra burden for packages such as asdf ;) astropy/astropy-helpers#314 (comment)
Reacted by P. L. Lim@drdavella , if you can somehow charge ASDF WBS for this work, that would be awesome... But if you charge to WBS, chances are the packages would be "required" to live in
spacetelescopeinstead of your own GitHub orastropy. Food for thought.Can you add non stsci people to have commit rights to a spacetelescope repo? If yes, that even that requirement shouldn't be an issue I guess? Even then, should it be the original, or a fork is enough?
It's possible that other projects (e.g. asdf) want to make use of astropy's test runner without having a hard dependency on astropy core. Would it make sense to move the test runner to
astropy_helpersor even to a completely separate repository? I found some discussion about this here but I didn't see any issues explicitly addressing a change.