astropy
astroquery.noirlab
I see that astroquery.noirlab 0.4.2 still points to the now deprecated/defunct https://astroarchive.noao.edu rather than the new https://astroarchive.noirlab.edu
SSLError: HTTPSConnectionPool(host='astroarchive.noao.edu', port=443): Max retries exceeded with url: /api/version (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:852)'),))
Simply changing the server name in the configuration also doesn't work for me either, although that may very well be due to my limited experience with astropy/astroquery config.
Does astroquery.noirlab need to be updated altogether to reflect these changes, or is there a quick work-around I can use for now?
I'm not sure what the right approach is here. @pothiers , any suggestions?
I'll look for a quick work around in a couple days. However, there is a bigger issue. The release schedule for AstroArchive is much quicker than AstroQuery. We would love to be able to update the AstroQuery client to make use of the far greater features of the current AstroArchive API. Alternatively, we plan to provide a AstroArchive client that we update every time there is a backward incompatible change with the Server. @keflavich Is there a published release schedule for AstroQuery?
Astroquery operates in a continuous deployment model. The latest master is intended, at all times, to be the latest release. We generally will not publish numbered releases except when there are major infrastructure or architecture changes.
Just wanted to note that I've encountered this same issue with version 0.4.5, it seems the code is still pointing to the noao.edu domain. I've separately done a PR to update the docs (#2324), but a simple url substitution here doesn't seem to work.
Modifying the domain name to noirlab.edu results in a Exception that astroquery.noirlab is expecting version 2.0 of the API and the API is responding with 6.0. (I assume this is related to what @pothiers mentioned about release schedules).
