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

Skip to content

Conversation

astrofrog
Copy link
Member

@astrofrog astrofrog commented Jul 26, 2025

This indicates whether the WCS class is preserving the original units from the header or set programmatically, or whether some units may have been converted to SI or degrees. Not adding a changelog entry since this just affects a feature added in dev.

  • 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.

… is preserving the original units from the header or set programmatically, or whether some units may have been converted to SI or degrees
@astrofrog astrofrog added this to the v7.2.0 milestone Jul 26, 2025
@astrofrog astrofrog requested a review from mcara as a code owner July 26, 2025 20:28
@astrofrog astrofrog added Affects-dev PRs and issues that do not impact an existing Astropy release no-changelog-entry-needed labels Jul 26, 2025
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.

@github-actions github-actions bot added the wcs label Jul 26, 2025
@pllim
Copy link
Member

pllim commented Jul 28, 2025

Do you want to at least amend the original change log to mention this new property?

Comment on lines +3596 to +3597
If `True`, units are always kept as specified, whereas is `False`, some
units may in some cases be converted to SI or degrees.
Copy link
Contributor

Choose a reason for hiding this comment

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

Don't commit suggested change - it is for illustration only but I would prefer a little bit mode details (for the users) on what this does.

Suggested change
If `True`, units are always kept as specified, whereas is `False`, some
units may in some cases be converted to SI or degrees.
If `True`, units are always kept as specified in/by header's CUNIT keywords, whereas is `False`, some
units may in some cases (excluding -TAB axes type) be converted to SI or degrees.

"some units in some cases" sounds vague.

@@ -424,10 +424,12 @@ def __init__(
fix=True,
translate_units="",
_do_set=True,
preserve_units=False,
preserve_units=None,
Copy link
Contributor

Choose a reason for hiding this comment

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

Why None?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Affects-dev PRs and issues that do not impact an existing Astropy release no-changelog-entry-needed wcs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants