Repository navigation
Add VO Cone Search - #859
Conversation
|
That is understandable. Any date planned for 0.3.6? |
|
Nope, usually we don't have any release dates. Whenever something big gets in @keflavich does a release. 0.3.5 is very much due to get released as there were tons of fixes to |
f9aa77c to
7734f8b
Compare
|
Can we ignore the "coverage decrease" warning? I believe it is misleading because the meat of my tests requires remote data. Here is the test result for |
|
@pllim - Sure, don't worry about coverage when adding a new module. |
7734f8b to
61afb8b
Compare
|
FYI -- CI report is in the first (rebased and squashed) commit. I skipped CI for the second commit because it is only PEP8 fix and PEP8 test is allowed to fail anyway (I was just being OCD). |
|
This will definitely need a changelog entry. |
|
@bsipocz , there is no "0.3.6" section in change log yet, but I'll be happy to add it when the change log has the relevant section (or if you decide to include this in 0.3.5). Please let me know. |
|
OK, sure. Let's add this to 0.3.5. |
|
This is somewhat overwhelming to review. @pllim can you suggest any particular sections to review that are specific to the astropy->astroquery migration? I assume much of this has undergone review when being incorporated into astropy? |
|
@pllim One general comment: There are lots of |
|
Re: @keflavich Oh, the original PR in Astropy (astropy/astropy#552) only had like 181 comments... I would recommend that you start with the following order:
While I implemented Since Cone Search already has its own async interface that works, I also decided against In short: Focus on the Astroquery common API and high level stuff, and feel free to ignore the validator if you want. The low level stuff should stay as-is. |
| def __getattr__(self, what): | ||
| """Expose ``executor`` and ``future`` methods.""" | ||
| try: | ||
| return getattr(self.executor, what) |
There was a problem hiding this comment.
Just throwing in some random stuff: getattr takes a third argument in case it encounters an AttributeError. However return getattr(self.executor, what, getattr(self.future, what)) might be hard to swallow 😄
There was a problem hiding this comment.
Oh, that's good to know. And I agree with your second sentence. 😄
|
Re: @MSeifert04 -- Yes, it was on purpose (pretty hard to type those things by accident 😂 ) but it was also written a long time ago. Since Sphinx isn't complaining, I have no motivation to revisit them. |
|
@pllim Just out of interest: Do you know why you did that on purpose? |
754831a to
013211f
Compare
|
@pllim - If you have added the most common common API functions/methods then there is no need to list it under the "does not follow..." section. |
|
@bsipocz -- Thanks for the feedback. I have attached a change log entry in the second commit. @MSeifert04 -- I am sure I knew why back in 2012 but now I have to guess... Maybe I was telling myself that "explicit is better than implicit" or maybe I just copied and pasted from someone... |
| - TAP/TAP+ - added Table Access Protocol utility and the ESAC | ||
| Science Data Centre (ESDC) extension. | ||
| - VO Cone Search - added module to access Virtual Observatory's Simple | ||
| Cone Search. This is ported from ``astropy.vo``. |
There was a problem hiding this comment.
Could you add the PR number? We don't yet let astrobot loose on this repo, but I have high hopes it.
|
CIs passed. The failure was reported only by coverage, which we have agreed to ignore. FYI. |
keflavich
left a comment
There was a problem hiding this comment.
I only found one small thing to comment on. I think this is ready to merge.
|
|
||
| def __init__(self): | ||
| if not self.URL.endswith(('?', '&')): | ||
| raise InvalidAccessURL("url should already end with '?' or '&'") |
There was a problem hiding this comment.
I don't think 'already' fits here.
There was a problem hiding this comment.
Do you mean removing that word from the error message, or just not check it at all?
|
Just that word
|
Also added change log entry and addressed feedback comments.
107adfe to
eaa6df9
Compare
|
Okay, done. I rebased, squashed, and letting CIs run one more time. |
|
Give @keflavich approved it I dared to hit the button. Other things are sorted out for 0.3.5, too, so maybe it's release time? :) |
This is the first step towards astropy/astropy#5558.
If this is merged soon enough, maybe on the Astropy side, we can start issuing deprecation warnings in v2 and completely remove it in v3, but that discussion belongs in Astropy.