-
-
Notifications
You must be signed in to change notification settings - Fork 390
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
eJWST release #2238
eJWST release #2238
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2238 +/- ##
==========================================
+ Coverage 62.20% 62.38% +0.17%
==========================================
Files 131 131
Lines 16772 16777 +5
==========================================
+ Hits 10433 10466 +33
+ Misses 6339 6311 -28
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding some non mocked remote tests would be great, otherwise I have one comment to address and this is good to go.
astroquery/esa/jwst/core.py
Outdated
@@ -1239,4 +1241,7 @@ def get_decoded_string(str): | |||
return str | |||
|
|||
|
|||
Jwst = JwstClass() | |||
if "pytest" in sys.modules: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think it's right to have this here in the main code, all testing stuff should be handled in the test files.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with you, I was thinking on how to avoid connection errors on this, now I have found a workaround using try/except in get_status_messages method
Co-authored-by: Brigitta Sipőcz <b.sipocz@gmail.com>
Hi @bsipocz, I have solved your comment about pytest in the main code, and added some additional tests. Regarding remote-data tests, as there will be data after launch in the archive, but not right now, we will include them when we have some static datasets to be used in the tests. Please do not hesitate to contact me in case you have further comments. On the other hand, I would like to ask you about the release of v0.4.5, after this code has been merged. When do you think we could have this version available? |
We said it should be out by the launch. Is that still a good timeline? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, let's get this in now. if needed, incremental smaller PRs are more than welcome (one is certainly needed to remove the disclaimer from the docs once the archive is fully operational).
Thanks @jespinosaar! |
Dear @bsipocz , @keflavich:
Now we are ready for the operational release of eJWST astroquery module, so, as we agreed, I have uploaded the operational URLs. Thanks for your support!