Closed astrofrog closed 4 years ago
I can do that this afternoon.
I'm more and more on the side that we shouldn't conda package the infrastructure packages, but suggest and only support pip install for them. That would resolve the issues people running into with outdated (but conda up-to-date) plugins, etc.
I'm curious to see if adding automerge to feedstocks will help (though in this case it wouldn't have).T auto-tick-bot + automerge should make keeping this up to date painless.
I do wonder whether we still need our own channel.
automerge is great, but it wouldn't have helperd here.
I'm +1 to keep the own channel. It helps to ensure default is used along with the astro packages rather than the conda forged builds.
It looks like pytest-astropy 0.8 is missing from conda-forge and the astropy channel - I think because we first need to create a recipe for pytest-subpackage-filter (added as a dependency in pytest-astropy 0.8). Anyone able to set up the recipe for pytest-subpackage-filter?