Dependencies cycle with Astropy to run tests

[Hellseher]

I've faced with this issue during preparing this project for Guix when update Astropy to 6.0.0 requires it as external package.

According to tox.ini requires astropy itself to run tests:

This project:

astropy-iers-data/tox.ini

Lines 9 to 18 in 1198afe

	deps =
	git+https://github.com/astropy/astropy
	extras =
	test
	commands =
	pip freeze
	pytest --pyargs astropy.coordinates -m "not hypothesis" {posargs}
	pytest --pyargs astropy.time -m "not hypothesis" {posargs}
	pytest --pyargs astropy.utils.iers -m "not hypothesis" {posargs}

Astropy project:
https://github.com/astropy/astropy/blob/9ce2087bd81f9502c4fdb87168d1cccd1aee4f53/pyproject.toml#L41-L47

Is there any other way to test the project without astropy?

Thanks.
Oleg

[pllim]

This package is meant to be used by astropy. Why would you want to test this package without astropy?

You should install both first before testing any of them.

[astrofrog]

We could certainly include some basic tests here that aren't astropy-dependent.

[Hellseher]

Hi,

Thank you for your replay.

The issue is that each package is built separately in isolated environment to
provide 100% reproducibility, one of the phase is to run unit tests:

to test astropy-iers-data -> install astropy -> install astropy-iers-data -> to test astropy-iers-data -> to head...

@astrofrog Any unit tests which do no require astropy would be great. To run tests of astropy would have no issues.

[pllim]

@astrofrog , we need to figure this out quick because job is failing now that prevents data update. See #27 for more details. Thanks!

[neutrinoceros]

It looks to me that this has been resolved already; I don't see a dependency cycle anywhere in pyproject.toml or tox.ini. Actually the tests directory is now effectively empty (save for an empty __init__.py), so I'm not even sure where tests would be collected from. Is there any important history that I'm missing ? Should we close this ?

[pllim]

@neutrinoceros , I think that is the problem. As stated in original post, one needs to actually run the astropy test suite to test this package. The issue author desires a way to test this package independently.