astropy / pytest-remotedata

Pytest plugin to control whether tests are run that have remote data
BSD 3-Clause "New" or "Revised" License
23 stars 15 forks source link

Update conda-forge and astropy conda packages to 0.3.2 #47

Closed hugobuddel closed 4 years ago

hugobuddel commented 4 years ago

The conda packages for pytest-remotedata on the conda-forge and astropy channels are still 0.3.1. The package on anaconda and main is 0.3.2.

These do not incorporate the LooseVersion change and therefore fail with pytest 6.0.0rc1 that was released last week (because "6.0.0rc1" is not a StrictVersion).

Can we therefore upgrade the astropy and conda-forge versions to 0.3.2? Or perhaps just remove them altogether? (As it seems that the anaconda channel has all versions of pytest-remotedata anyway.)

Some of CI runs broke because we had conda-forge as a higher priority channel than anaconda ('defaults') and did not specify a version. We have now hardcoded pytest-remotedata 0.3.2 (or higher) as a depency, so it will automatically pickup the anaconda one anyway and our immediate problem is solved.

Pytest 6.0.0 will probably be released soon too, which will also resolve the problem (until some other rc version is released).

pllim commented 4 years ago

@mwcraig , do you handle the conda releases for this package? Thanks.

mwcraig commented 4 years ago

@pllim -- yes; will make a couple changes to https://github.com/conda-forge/pytest-remotedata-feedstock/pull/6 later today and then merge. Needs some dependency updates and maybe a couple more things.

Thanks for the ping!

mwcraig commented 4 years ago

I just merged https://github.com/conda-forge/pytest-remotedata-feedstock/pull/6 which should fix this. It will be roughly ~1 hour until it shows up in conda.

pllim commented 4 years ago

Thank you!

hugobuddel commented 4 years ago

https://anaconda.org/search?q=pytest-remotedata still shows 0.31 for the conda-forge and astropy channels. The specific problem with pytest is gone though, because they released 6.0.0 and later.

mwcraig commented 4 years ago

Working on the fix....

mwcraig commented 4 years ago

Fixed now, thanks for reporting.