Skip to content

Comments

Add ESO catalogue functions#3531

Open
ashleythomasbarnes wants to merge 13 commits intoastropy:mainfrom
eso:develop-catalogues
Open

Add ESO catalogue functions#3531
ashleythomasbarnes wants to merge 13 commits intoastropy:mainfrom
eso:develop-catalogues

Conversation

@ashleythomasbarnes
Copy link

@ashleythomasbarnes ashleythomasbarnes commented Feb 13, 2026

We've added functions in the same structure similar to the others to query the ESO catalogues:

  • list_catalogues -> lists all available catalogues
  • query_catalogue -> query results for a specific catalogue with constraints

Docs are coming in another PR.

-- Thanks!
@juanmcloaiza @szampier @almicol

@ashleythomasbarnes ashleythomasbarnes changed the title Add ESO catalogue functions (#8) Add ESO catalogue functions Feb 13, 2026
Comment on lines 16 to 20
eso
^^^

- Add functionality to list and query ESO catalogues. [#8]

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I seem to remember that this file is normally edited by the astroquery maintainers

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nope, this is correct, preferably the changelog entry is added in the PR by the PR author.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let me know if you need more here...

@szampier
Copy link
Contributor

General comment: it’s a bit difficult to focus on the new feature since the PR also contains many formatting changes. Splitting these into a separate commit or PR would make the review easier.

@bsipocz bsipocz added the eso label Feb 13, 2026
@bsipocz bsipocz added this to the 0.4.12 milestone Feb 13, 2026
Copy link
Member

@bsipocz bsipocz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've started reviewing this, but the code style changes are a bit overwhelming, so I stopped when I got to the actual changes in core.py.

Could you please remove any of the style changes (and anyway, please don't force short line length on code) and force push back the actual code changes?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file is not needed any more, please remove.

Comment on lines -19 to +21
tap_url = _config.ConfigItem(
tap_obs_url = _config.ConfigItem(
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is technically an API change; but for now it is acceptable as we haven't yet released the ESO refactor work.

Comment on lines 36 to 52
from ..exceptions import (
RemoteServiceError,
LoginError,
NoResultsWarning,
MaxResultsWarning,
)
from ..query import QueryWithLogin
from ..utils import schema
from .utils import _UserParams, raise_if_coords_not_valid, _reorder_columns, \
_raise_if_has_deprecated_keys, _build_adql_string, \
DEFAULT_LEAD_COLS_PHASE3, DEFAULT_LEAD_COLS_RAW
from .utils import (
_UserParams,
raise_if_coords_not_valid,
_reorder_columns,
_raise_if_has_deprecated_keys,
_build_adql_string,
DEFAULT_LEAD_COLS_PHASE3,
DEFAULT_LEAD_COLS_RAW,
)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I really wish these type of style refactorings would not be mixed into feature branches.

Also, we do allow longer lines in astroquery, up to 120 characters, so please don't apply these black type spreads over many lines.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

@ashleythomasbarnes
Copy link
Author

Indeed this should have been a draft PR like we agreed (sorry @szampier)... How should we proceed - shall I revert to draft and make changes, or okay to keep as-in?

@ashleythomasbarnes
Copy link
Author

Okay, I cleaned up my mess - it should be clearer now. Let me know how you want to proceed...

@codecov
Copy link

codecov bot commented Feb 13, 2026

Codecov Report

❌ Patch coverage is 74.35897% with 20 lines in your changes missing coverage. Please review.
✅ Project coverage is 72.69%. Comparing base (de342ea) to head (db96c8b).
⚠️ Report is 7 commits behind head on main.

Files with missing lines Patch % Lines
astroquery/eso/core.py 72.97% 20 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3531      +/-   ##
==========================================
- Coverage   72.71%   72.69%   -0.02%     
==========================================
  Files         219      219              
  Lines       20473    20543      +70     
==========================================
+ Hits        14886    14934      +48     
- Misses       5587     5609      +22     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@ashleythomasbarnes
Copy link
Author

Just to let you know @bsipocz - I spoke with @juanmcloaiza and @szampier this morning, and we're happy for you to continue the review. I will be away from 1st March until ~ 7th April, so it would be great if we could get this wrapped up by then, otherwise @juanmcloaiza has offered to take over any needed changes whilst I'm gone. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants