Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

eerovaher
Copy link
Member

Description

I am simplifying coordinates.concatenate_representations(). That functions makes use of the _concatenate_components() function. Slightly expanding the private function allows removing some duplicated code from concatenate_representations(), so that change is included here too.

  • By checking this box, the PR author has requested that maintainers do NOT use the "Squash and Merge" button. Maintainers should respect this when possible; however, the final decision is at the discretion of the maintainer that merges the PR.

Copy link
Contributor

Thank you for your contribution to Astropy! 🌌 This checklist is meant to remind the package maintainers who will review this pull request of some common things to look for.

  • Do the proposed changes actually accomplish desired goals?
  • Do the proposed changes follow the Astropy coding guidelines?
  • Are tests added/updated as required? If so, do they follow the Astropy testing guidelines?
  • Are docs added/updated as required? If so, do they follow the Astropy documentation guidelines?
  • Is rebase and/or squash necessary? If so, please provide the author with appropriate instructions. Also see instructions for rebase and squash.
  • Did the CI pass? If no, are the failures related? If you need to run daily and weekly cron jobs as part of the PR, please apply the "Extra CI" label. Codestyle issues can be fixed by the bot.
  • Is a change log needed? If yes, did the change log check pass? If no, add the "no-changelog-entry-needed" label. If this is a manual backport, use the "skip-changelog-checks" label unless special changelog handling is necessary.
  • Is this a big PR that makes a "What's new?" entry worthwhile and if so, is (1) a "what's new" entry included in this PR and (2) the "whatsnew-needed" label applied?
  • At the time of adding the milestone, if the milestone set requires a backport to release branch(es), apply the appropriate "backport-X.Y.x" label(s) before merge.


if any(
"s" not in r.differentials or type(r.differentials["s"]) != dif_type
Copy link
Member Author

Choose a reason for hiding this comment

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

The function already checked a few lines earlier that "s" is in all r.differentials and raised a ValueError if that wasn't the case, so checking it again here was redundant.

Copy link
Contributor

@mhvk mhvk left a comment

Choose a reason for hiding this comment

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

Nice simplification. Inline a suggestion for a further simplification - plus two nitpicks that you should feel free to ignore.

values = _concatenate_components(
[r.differentials["s"] for r in reps], dif_type.attr_classes.keys()
dif_type = type(differentials[0])
if any(type(differential) is not dif_type for differential in differentials):
Copy link
Contributor

Choose a reason for hiding this comment

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

Probably not worth rerunning CI for, but could be ... in differentials[1:]

@@ -275,15 +275,17 @@ def get_constellation(coord, short_name=False, constellation_list="iau"):
return names


def _concatenate_components(reps_difs, names):
def _concatenate_components(reps_difs, target_type):
Copy link
Contributor

Choose a reason for hiding this comment

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

I like the change, but think when we go here anyway, we might as well make it even simpler by just using reps_difs[0].attr_classes below and not pass in target_type altogether.

In principle, could also do the check that all the classes are the same here, but then it would change the error message, so probably not worth it.

rep_type = type(reps[0])
if any(type(r) != rep_type for r in reps):
if any(type(rep) is not rep_type for rep in reps):
Copy link
Contributor

Choose a reason for hiding this comment

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

Could do ... in reps[1:]

@mhvk
Copy link
Contributor

mhvk commented Aug 11, 2025

p.s. I forgot to mention: #18193 will replace concatenate_representations(). I do intend to pick that back up, but am fine with getting this in beforehand.

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

Successfully merging this pull request may close these issues.

2 participants