P. L. Lim

At a glance, I do not think so, but it would be obvious when the PR is out. 😉 https://github.com/astropy/astropy/blob/main/.github/workflows/ci_cron_weekly.yml

`No module named 'astropy_iers_data'` Not sure who packages for "voici" but this team needs to add https://pypi.org/project/astropy-iers-data/ to their distro. `astropy` now requires it, so not sure why they didn't...

@JuanCab , is this issue considered resolved over here then? If so, please close the issue. Thanks!

`astropy.tests` is for testing, so it would import (optional) test dependencies. So, if this `voici` wants to run astropy tests too, then it should also opt to install the test...

Not sure how visible `PendingDeprecationWarning` really is. Would like to hear from `io.ascii` and `io.misc` active maintainers (@taldcroft @hamogu @dhomeier @matteobachetti )

Yes, `PendingDeprecationWarning` is pretty unintrusive but TBH I am not sure even downstream developers can see it. It is a struggle to get some of them to even test against...

(Does not hurt though to try. But only if we really going to upgrade that to DeprecationWarning at some point. There is no point to introduce a PendingDeprecationWarning and then...

Re: https://github.com/astropy/astropy/issues/14316#issuecomment-2252854108 Maybe a draft PR? 😸

Thank you. I left some preliminary comments. As mentioned in #16648 , we need to identify what truly belongs in core `astropy` library, and what is more appropriate downstream in...

> construction, access, and storage Would it make sense to subclass `scipy.stats.Covariance`? 💭