Astroquery: conesearch.list_catalogs uses stale URL

Created on 26 Jan 2018  路  9Comments  路  Source: astropy/astroquery

This routine uses the URL http://stsdas.stsci.edu/astrolib/vo_databases/conesearch_good.json, which is a deprecated webpage.

vo_conesearch

Most helpful comment

@pllim @StuartLittlefair The rules on the web server have been changed to allow access to astrolib/vo_databases/.*.

Note: This URL will likely change at some point in the future though.

All 9 comments

Aww, man. I think this is a side effect of what @SaraOgaz implemented yesterday. Sara, is there a way to revive just stuff under vo_databases? Please advise.

c/c @jhunkeler and @rendinam or alternative in-house solutions.

@pllim @StuartLittlefair The rules on the web server have been changed to allow access to astrolib/vo_databases/.*.

Note: This URL will likely change at some point in the future though.

Thanks for the quick fix, @jhunkeler !

@bsipocz and @keflavich , we have 2 options:

  • Backward-incompatible: Change the URL and only support the next release with this new URL.
  • Backward-compatible: Change the URL and backport this change to all supported versions.

Please advise.

What is the consequence of leaving the current version with the outdated URL? We've never done any backporting in astroquery before, we just make new releases. Partly, we do this because the services themselves are (ideally slowly) moving targets; there is no real expectation that older versions of astroquery should work at all.

What is the consequence of leaving the current version with the outdated URL?

Ideally, we wouldn't retire outdated URL until the next release (0.3.8). But then, once retired, vo_conesearch in the older versions (< 0.3.8) would not work anymore. User will have to upgrade. Does that sound reasonable to you? Do you have a tentative timeline for 0.3.8 release?

We were thinking about doing a follow up move of those pages end of February, but we can extend it a little if needed.

0.3.7 has just been released. There isn't a strict timeline, but normally we have at least a few month between releases to get some new features added for the new one.

However, we already have two big "new service" PRs almost ready, so I think it's fine to get a new release out once both of them are merged in.

Update: New URL is in place and the old one is redirecting to the new one already (thanks to @jhunkeler ). #1033 should update vo_conesearch to the new one entirely.

Was this page helpful?
0 / 5 - 0 ratings