Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Remove deprecated code in BaseCoordinateFrame #15500

Merged
merged 1 commit into from Oct 17, 2023
Merged

Remove deprecated code in BaseCoordinateFrame #15500

merged 1 commit into from Oct 17, 2023

Conversation

eerovaher
Copy link
Member

Description

The code deprecated in #10475 should be removed in astropy 6.0.

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

@eerovaher
Remove deprecated code in BaseCoordinateFrame
8000bb4 
This is a follow-up to b0d2c93
(Deprecate passing an uninstantiated frame class to
BaseCoordinateFrame.transform_to()).
@eerovaher eerovaher added coordinates API change PRs and issues that change an existing API, possibly requiring a deprecation period labels Oct 17, 2023
@eerovaher eerovaher added this to the v6.0 milestone Oct 17, 2023
@github-actions
Copy link

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?
  • Is a milestone set? Milestone must be set but we cannot check for it on Actions; do not let the green checkmark fool you.
  • 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.

@eerovaher eerovaher requested a review from mhvk October 17, 2023 21:20
mhvk
mhvk approved these changes Oct 17, 2023
View reviewed changes
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.

Yes, nice to get rid of the cruft!

@mhvk mhvk merged commit 98d82dd into astropy:main Oct 17, 2023
26 of 30 checks passed
@eerovaher eerovaher deleted the no-frame-transform-to-class branch October 17, 2023 22:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@mhvk mhvk mhvk approved these changes

Assignees
No one assigned
Labels
API change PRs and issues that change an existing API, possibly requiring a deprecation period coordinates
Projects
None yet
Milestone
v6.0.0
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@eerovaher @mhvk